title: Finding link time bottlenecks
body: <p>A question I haven't seen answered that I'm finding very interesting. All the other threads seems to discuss forcing the problem, ie switching to dynamic linking or just distributing the workload. I'm more interested in actually finding out what's causing linking to take so long. </p>
  
  <p>The problem is that I don't really see any official ways to get the relevant metrics from the linker, at least not for the VS linker. There's the /verbose switch which will give you a lot of insight into what the linker is doing, but it won't give you any fine grained timings at all. </p>
  
  <p>I've been thinking of running the linker process from a tool which do the actual measurements on a per line basis. While this won't provide accurate timings, it would probably be accurate enough to pinpoint linking bottlenecks.</p>
  
  <p>Anyone know of a better approach, or perhaps even a tool for this task?</p>