|My coworker has a brand new 16GB laptop.
16GB should be enough for most workloads, or so you'd think.
Unfortunately, that is not the case.
We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc.
Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes.
We're getting timeouts like you wouldn't believe, nothing works.
After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%.
I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem.
At this point it's become unworkable.
You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower.
But instead, SQL Server just pretty much stops working altogether.
Closing a VS instance fixes the problem, but sometimes we just need to have two instances open.
My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right.
Anyone have any ideas what the problem could be?*
* Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.