slow linker time: Link.exe excessive PF delta

Hot Topic

Copy contents of int to float
How to create log file using mfc?
error C2220: warning treated as error
How to Copy form CDC dcMem1 to CDC dcMem2?
Compile warning D4024 and Link error LNK1181
Missing Class Designer for VS2005 C++/CLR projects
Documentation for struct RUNTIME_FUNCTION
Standard C++ library linker error
Gettin started with Visual C++
EVC++

Visual C++

vector<bool>::iterator problem
Mixing C and C++ MFC
failed assertions leave code running behind the message box?
DeviceIoControl does not work when query LCD brightness
Calling .NET DLL from VC++
No Symbols Loaded
print string from the enum pointer
calling a WINAPI function from a managed main creates linker error
Help ?
visual c++ dll

slow linker time: Link.exe excessive PF delta

Recently a dll that use to link in under 1 minute has started taking over 20 minutes to link. During that time, link.exe isn't using the processor at all and it is constantly page faulting. The mem usage on link.exe is around 60 MB. When my co-workers link the same project their link time is normal with link.exe fully using the processor and consuming around 250MB. Any ideas on how to force link.exe to use more memory so it isn't constantly page faulting



Answer this question

slow linker time: Link.exe excessive PF delta

  • tjswingle

    Do you use /GL and the Linker /LTCG switch If so, turn it off it makes linking horribly slow.

  • astrof

    What happens when you exit and restart Visual Studio and relink

  • First Available

    No luck. I have even done complete clean source code builds. The problem is now chronic for all my projects. (The others are small so the delay is less.) I think something is messed up with my .NET installation. I am about at the point of reinstalling Visual Studio .NET.

  • freaky roach

    One thing to consider is disk fragmentation. If you have a lot of solutions, projects, and files; that you have been working on over time, the likelihood of all the source files being fragmented is very high. This would cause the system to be slower then normal during a compile/link.

    Try cleaning all projects (debug and release)--cleaning all that chaff before defrag makes it much faster--and running defrag to see if that helps.



  • tomazos

    I encountered similar situation. Link.exe consumes more than 400MB memory and takes about 10 minutes to build a 12 MB dll file. All my co-workers encountered the same situation. There are about 170 projects in this solution and will be linked to one dll. We were using VC6 before and tooks only 2 or 3 minutes. After moving to VC8, it takes 10 minutes ( only linking, not including compiling). Can anyone help Thanks.

  • maheer

    None of the above was applicable. And I already had defrag'd my disk and done a clean "get" of the code. I am convinced the issue is one with link.exe isn't using enough memory for some reason. I'll file a bug as suggested.

    thanks,

    al.

  • graffy

    If the above doesn't work, then please log a bug at the product feedback center (http://connect.microsoft.com/Main/content/content.aspx ContentID=2220).

    Thanks,
    Ayman Shoukry
    VC++ Team


  • slow linker time: Link.exe excessive PF delta
Answer this question