Hacker News new | ask | show | jobs
by hackinthebochs 4954 days ago
Oh sure it is. I use a Dell laptop with 4GB of ram running visual studios (sometimes two instances), full blown SQL Server, SQL Server management studio (graphical database client), Chrome with a bajillion tabs and a handful of corporate-required background applications. I still don't get any noticable lag due to paging.
2 comments
WhaleBiologist 4954 days ago
That's fine if the projects you are loading in Visual Studio are reasonably sized. If you load a single monolithic legacy solution, the Intellisense database is huge, and you run into cases where you have to close every single thing other than Visual Studio just to have enough memory to load all the debugging symbols when debugging the application. Life got so much better when we switched to 64 bit Windows 7.
link
binarycrusader 4954 days ago
I strongly disagree. As someone that has done quite a bit of development work on a laptop with only 4GB of memory, I can tell you right now that life was significantly better after I upgraded to 8GB.
link
bcoates 4954 days ago
If the built-in disk has low enough latency, your memory needs go way down as giant predictive disk caches become unnecessary and swapping is less of a performance killer.

Moving to SSD let me put a VM on my 8GB laptop that stole half the RAM without destroying my ability to run a couple of visual studios, office and a pile of chrome tabs. Under 4GB and spinning disk that was unworkable.

RAM needs might be stagnating for a few years as high-performance flash becomes commonplace and applications don't have to be as aggressive about keeping everything in memory.

link
binarycrusader 4954 days ago
You're suggesting that dramatically shortening the lifetime of my SSD through needless writes is better than simply adding more memory?

And what if my working set is incapable of fitting into that measly 4G of memory (which likely will only be 3GB at most once the OS and Visual Studio is loaded) even with swapping? I can tell you right now that's easy to do with Visual Studio with even "relatively" small applications once you start loading debug symbols.

link