Improve link time of large C++ application with SSD Drive

Question

0.00/5 (No votes)

See more:

Dear,

We are developing large C++ application. Link time of debug target is one of our biggest irritant here (we build C++ native applications). In fact, that's our biggest problem related to our usage of Visual Studio (2005, 2008 and 2010). We know that the main bottleneck is the Hard Drive.

Intel is proud to announce that X25 SSD Drive can improve development time ( http://www.intel.com/design/flash/nand/extreme/index.htm[^] ). I cannot find any benchmark specific to link time.

Is there someone who tried this kind of drive on large C++ project ? What are the impact on link time of debug target ?

If you want more details about our experimentations:
http://www.codeproject.com/Messages/3288308/Minimized-link-time-of-Cplusplus-applications.aspx[^]

Regards,

Frédéric Hébert

Edited by the linky police. :)

Posted 19-Oct-10 9:51am

Fred Hebert

Updated 19-Oct-10 13:07pm

Henry Minute

v2

Add a Solution

Comments

AspDotNetDev 19-Oct-10 20:53pm

Non-answer posted by Ted2102 (http://www.codeproject.com/script/Membership/View.aspx?mid=6284671): Haven't tried it, but interested in the result. Are you already using a SAS RAID array?

Fred Hebert 20-Oct-10 14:05pm

No we didn't tried SAS Raid array. Maybe we should,

Like I said on my previous post regarding link time, we reduce link time a lot using computer with lot of RAM. The disk read cache help reducing link time a lot. We think that the remaining bottle neck is writing of PDB file.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

basementman · Answer 1 · 2010-11-09T03:53:00

Solution 2

Another, free, alternative is to create subprojects that stick seldom-changing objs into a LIB file and then just link to the LIB files in your main build. Much quicker (what we used to do in the 80's/90's with MSC5.1/VC1.0).

Posted 9-Nov-10 3:53am

basementman