building code slow?
When i build some code i''m wondering how can i get this faster? more ram, more cpu speed, faster hd????
SigwarthSoft
sigwarthsoft@hotmail.com
icq#: 62538030
Maastricht, Netherlands
Stefan Sigwarth
February 05, 2000 06:14 PM
RAM and Harddrive speed are the biggest factors. I''ve found that RAM seems to be the most important element. You definately should have at least 128MB if your compiling large projects.
--TheGoop
--TheGoop
Faster hard drive is also important. If you''re using Visual C++, it generates a ridiculous amount of intermediate/secondary files. Not to mention if you just have enough includes going on, you''re accessing that many extra files per compilation. Mason, in a previous thread, recommended getting enough memory to create a ram-drive and compiling on that.
Or you could defrag your modem.That always makes my system run better.
DarthSpanky
Newbie Helper
(hehe)
P.S. Ignore me.
DarthSpanky
Newbie Helper
(hehe)
P.S. Ignore me.
February 10, 2000 04:18 PM
All the hardware factors in your list affect time of compillation, but the best way to make your compiles faster is to break program into modules and put those modules into different files. So only those files affected by the latest changes will be compiled.
Same time you will need to organize your work or you will
finish in the tons of little files for a big project, which will reduce readability of your program.
Fariz Alikishibekov,
www.warriormage.com
Fariz
Same time you will need to organize your work or you will
finish in the tons of little files for a big project, which will reduce readability of your program.
Fariz Alikishibekov,
www.warriormage.com
Fariz
Make sure your power supply uses the green electrons. That helps.
Seriously, though, you should check to see if you''re having to rebuild too many files. If you make some small changes, and hit build, does it have to rebuild 5-10 files? If so, you have a dependency problem and need to break up your header files along better boundaries.
Everything helps though. Work just upgraded me from a Pent2 200-something (64 Megs) to a Pent3 500 (128 Megs). Monster screams, at least when compiling on NT.
OK, done bragging now.
Seriously, though, you should check to see if you''re having to rebuild too many files. If you make some small changes, and hit build, does it have to rebuild 5-10 files? If so, you have a dependency problem and need to break up your header files along better boundaries.
Everything helps though. Work just upgraded me from a Pent2 200-something (64 Megs) to a Pent3 500 (128 Megs). Monster screams, at least when compiling on NT.
OK, done bragging now.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement