http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Looks like unit tests to me... How many individual unit test assemblies do you have? http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment9http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment9Sun, 26 Oct 2008 07:50:50 GMTHmmm...my VS Memory hovers around 150 MB consistently and I have a solution with 35 projects in it. http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment8http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment8Tue, 21 Oct 2008 20:01:35 GMTMy 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. http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment7http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment7Mon, 20 Oct 2008 16:02:26 GMTI'm with Joe here... However did you ever get VS down to 150MB? http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment6http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment6Thu, 16 Oct 2008 13:45:08 GMTunit tests consume up to 1.5 gig of memory, at peaks, but we know it's because of a memory bug. http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment5http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment5Thu, 16 Oct 2008 06:29:44 GMTThe 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? ;-) http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment4http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment4Wed, 15 Oct 2008 19:33:37 GMTJoe, 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. http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment3http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment3Wed, 15 Oct 2008 17:56:34 GMTGood grief, what are you doing? Sometimes I find we do things big just because we can, rather than because we need to. http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment2http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment2Wed, 15 Oct 2008 17:23:49 GMTI'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.... http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment1http://ayende.com/3651/do-you-think-that-i-have-a-heavy-weight-build-process#comment1Wed, 15 Oct 2008 17:08:35 GMT