Well, it was worth a try
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
- How much RAM does your PC have? If it is low, and the OS is using virtual memory then this will slow down everything. 2) If you are paging, you also should move the page file location onto a separate disk location that won't interfere with read/write operations of other actions
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
40 Seconds? Poor guy. A full rebuild takes me 17 minutes (significantly more on other machines). VS 2008 seems to be more CPU-Bound than VC6. going from a "good normal" disk to an SSD gives me about 10% improvement, not worth the trouble. The next step will probably be decoupling some projects, so more can build in parallel.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
- How much RAM does your PC have? If it is low, and the OS is using virtual memory then this will slow down everything. 2) If you are paging, you also should move the page file location onto a separate disk location that won't interfere with read/write operations of other actions
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Intel Core 2, Quad-Core, WinXP 32-bit, 4GB DDR3 RAM. (I was testing without other software open except normal services) I'm guessing the file operations are not as significant as I always thought during a compile. No biggy. I just spent a lot of time revamping my array, reloading the OS, all my software, so it was kind've a let down in the end but I had been wanting to try it, just to see if it would change anything.
-
40 Seconds? Poor guy. A full rebuild takes me 17 minutes (significantly more on other machines). VS 2008 seems to be more CPU-Bound than VC6. going from a "good normal" disk to an SSD gives me about 10% improvement, not worth the trouble. The next step will probably be decoupling some projects, so more can build in parallel.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
That's why you measure first. ;P
Wout
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
Possible that the project size is just too small to really use the "power" of the raid; for example, most of the time is spent setting up the build than compiling and building the files/project. 40 seconds for a full rebuild, it must be "hello world1"!
Watched code never compiles.
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
Most of the compiling happens in temp folder. Did you change your temp directory to reside on raid0?
-
I have one Visual C++ solution that takes about 40 seconds to compile (full rebuild in debug mode) so I thought I'd try setting up most of my Raid array space with a RAID 1 volume for storage, and a teeny tiny little 30GB RAID 0 volume for a compile playground to see if performing the edit and compile on the RAID 0 would speed things up. Well it loads faster in the IDE but my compile times are identical. 40 seconds either way. Frack! :(( (and here I thought I was being slick)
Poor baby. Complete builds of our products take from 40 to 75 minutes on an 8 processor box with 16G of RAM.
Software Zen:
delete this; -
Possible that the project size is just too small to really use the "power" of the raid; for example, most of the time is spent setting up the build than compiling and building the files/project. 40 seconds for a full rebuild, it must be "hello world1"!
Watched code never compiles.
-
Most of the compiling happens in temp folder. Did you change your temp directory to reside on raid0?