|
Nowhere near that much. The only time the memory on my main dv box (a dual core Opteron with 5GB RAM) gets stretched is when I'm running multiple VMs.
That said, VS2008 is more hungry than (say) VS2003 for the same codebase. In our experience it's no worse (but more stable than) VS2005.
|
|
|
|
|
ed welch wrote: I can't imagine that it's such a resource hog that you need 8GB.
You're imagining the wrong problem. VS 2008 can take 1-2 GB on it's own though, typically on those projects with thousands of files. But the problem isn't really VS 2008, it's everything combined.
Most developers aren't just using the IDE, they also have the DB window open (i.e.: SQL Server), they'll be operating the app locally (i.e.: IIS working locally, web browser), they'll have Virtual Machines for testing and sometimes even for developing (i.e.: VPC, VMWare), they'll have task-tracker software open, some form of chat client, a copy of Outlook, some search client (like Google Desktop)
I'm on a laptop (Core 2 Duo and 2GB) and I would be pushing for more if I still programmed all that much.
Most software people make too much money to not be running some form of leading-edge configuration.
|
|
|
|
|
Hmm, I got 2GB and don't have any problems and I keep a ton of other stuff open at the same time. VS studio 2005 only uses 80MB max (for my projects at least, I only do c++).
|
|
|
|
|
C++ might be part of it.
I'm working on a one-year old ASP.NET project (C#) with a few hundred files in the project. We're also running generated data objects on a 200 hundred table DB, so you can imagine the amount of code we're have. Oh yeah, and we're running AJAX toolkit (more stuff to load into memory). Once it compiles everything and sets it all to debug, I'm easily at 800 MB.
Being in C++ might have something to do with it. But any of those projects that is a "core business" project tends to accumulate size very quickly. By the time we hit the 2-year mark, I'm sure I'll be asking for more RAM (but it seems a small price to pay for VS productivity).
|
|
|
|
|
Depends. Of the two solutions i most often have open, one loads at around 150MB, the other at just over 200MB. Nothing too bad, even when they're both open at once...
...until i fire up the debugger in either of those instances. Now the footprint balloons to over half a GB. Brutal.
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
The game engine I'm developing (currently 15-20k lines of unmanaged C++ with some inline assembler) takes about 120MB when doing light editing. Debugging does not seem to increase this by much.
Are you using .NET or native code? IIRC managed code is harder on the IDE.
|
|
|
|
|
azonenberg wrote: Are you using .NET or native code?
Both. Somewhere past 400KLoC of the former, a relatively small LoC for the former, plus a fairly big pile of Javascript that gets its own debugger when necessary.
azonenberg wrote: IIRC managed code is harder on the IDE.
Yeah... Mixed-mode debugging is the worst of all - i try hard to avoid it.
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
400K lines? I hope this isn't a solo project like mine...
|
|
|
|
|
Oh no. 
This is over a decade old, with scores of authors over the years and half a dozen currently maintaining and extending it. Too many cooks, you might say... 
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
The good thing with 8 gigs I've noticed, is that you can easily run 2-3 instances of VS2008, and 2-3 VMWare sessions at the same time, without any thrashing. On the other hand, the quad core CPU might have something to do with it.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
But as it's running 32-bit XP Pro - this is our IT department's spec (sometimes you just have to stop fighting) - it's really 3.25GB. Still, it's 2.25GB more RAM than in my last machine
|
|
|
|
|
Oooh you people make me green with envy! I have to run VS2008 on a loptap with 1Gb RAM, 1.6GHz single core, 20Gb h/disk. It seems to me that the larger the company, the smaller the development workstation. Admittedly, I've got access to virtual machines to do the actual testing on but they're at the other end of a double-bounce broadband connection (i.e. My office<-BB->Hub Site<-BB->VM site) and shared with a hundred other people so there's a bit of contention. If there's one thing this has taught me it's to write tight code with minimal decoration and let someone else grumble about what it looks like.
|
|
|
|
|
Well, VS 2008 is not bad - I run it on similar laptop with 3/4 of your memory, and with couple of DB servers running. It's only when I develop in Java NetBeans at the same time that NetBeans freezes  from time to time.
|
|
|
|
|
Dmitri,
You're right there. I find VS2008 to be infinitely preferable to VS2005 and it certainly does the job without complaint. Yes, I also run SQL Server, ADAM, Outlook and one or two other things in the background but there are some days that I... just... wish... it... was... a... bit... F-A-S-T-E-R!!!
|
|
|
|
|
surely there are others that dev on a overkill machine? + it's nice to be able to test your code on 3 os's without a reboot (vm's ftw)
DrewG, MCSD .Net
|
|
|
|
|
So your host os is Xp 64Bit, or Vista 64bit? Any compatability problems?
|
|
|
|
|
vista x64, and I have been thrilled with my results thus far. It is uncommon any more to run into something that just doesn't work in 64 bit, and if so, crack open vpc and problem solved
DrewG, MCSD .Net
|
|
|
|
|
Same here -- Vista x64 on a dual core 8 GB machine. Couldn't be happier. VM's also solve any testing/compatibility issues you can think of. All my target systems are in one box for testing!
|
|
|
|
|
I'm on a laptop with vista 32-bit. AFAIK my system (dell inspiron 1520) doesn't have 64-bit drivers available 
|
|
|
|
|
Join the club, got a quad core to, except I have only 4GB of memory on this machine.
VMWare rulez!
WM.
What about weapons of mass-construction?
"What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
My blog
|
|
|
|
|
Very true..
Visual Studio is known to be a resource hog..
My machine set up is quad-core 45nm q95450
Ram 8Gb DDR2 800
Tell you what, I never have to close any project window to save system's resource ever~!
Live for ASP.NET...
|
|
|
|
|
Nah.. I've got one too.. Running Vista x64 Ultimate with 8GB. While a little gunshy at first to install x64, I've been surprised to find that I haven't had any compatibility issues. Everything I use works great (VS 2008, VS 2005, Blend, Design, Illustrator, Photoshop, Virtual PC 2007, MS Office, etc). The hardware acceleration in Virtual PCs is astoundingly fast (I'm playing StartCraft on a XP Home Virtual PC right now). Have had this setup for almost 6 months now. Will never go back.
modified on Monday, August 4, 2008 2:23 AM
|
|
|
|
|
I agree, 8 gigs is nice when you run vm's I am a web developer so I don't really need vm's so often so four gig and my 45 nm Quad Core Xeon does the trick.
|
|
|
|
|
I'm a web developer also, and I find the VM's to be totally necessary when testing older browers: IE6, Fx2, and IE6 on Windows 2000. Unfortunately, we have to fully support all of those!
|
|
|
|
|
Yeah, I can relate to that, fortunately we don't have to as we create closed web applications for large government institutions, we only need to support the latest Firefox and IE fully. We use virtual machines too but only right before release to ensure our application works technically on older browsers but we don't have to fully support them.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
