FUTURE POSTS
- Expertise in the age of AI, or: Matt's Claude'll handle this - about one day from now
- 15+ years of working with coding agents - 6 days from now
- Putting Claude up against our test suite - 8 days from now
- The GPU Is the New Bangalore - 10 days from now
- Learning to code, 1990s vs 2026 - 14 days from now
There are posts all the way to May 05, 2026
Comments
I'm more interested in what kind of magical version of Visual Studio you have that you have going on that only consumes that much memory....
Good grief, what are you doing?
Sometimes I find we do things big just because we can, rather than because we need to.
Joe, when there is something consuming too much memory, the other programs will forced to use less. The virtual memory comes into play.
I think that's the reason.
The same happened to me a while ago, that was because I was using creating (by mistake) the NH SessionFactory in each test fixture. When I fixed that it fall below 100mb... I mean, are you sure there's not an error in your script/code? ;-)
unit tests consume up to 1.5 gig of memory, at peaks, but we know it's because of a memory bug.
I'm with Joe here... However did you ever get VS down to 150MB?
My Visual Studio.Net is consuming 636MB of ram right now. Visual Studio is not the most light weight IDE and I think Resharper adds to that footprint, albeit Resharpers footprint is well worth it.
Hmmm...my VS Memory hovers around 150 MB consistently and I have a solution with 35 projects in it.
Looks like unit tests to me...
How many individual unit test assemblies do you have?
Comment preview