Bug 800 - Slow linking on network disks (no output buffering?)
Summary: Slow linking on network disks (no output buffering?)
Status: RESOLVED WONTFIX
Alias: None
Product: binutils
Classification: Unclassified
Component: ld (show other bugs)
Version: 2.15
: P2 enhancement
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-23 21:34 UTC by Fredrik Huss
Modified: 2019-11-22 04:15 UTC (History)
2 users (show)

See Also:
Host: i686-pc-linux-gnu
Target: i686-pc-linux-gnu
Build: i686-pc-linux-gnu
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fredrik Huss 2005-03-23 21:34:41 UTC
Linking is slow for large programs if the output file is stored on a network   
disk (e.g. ClearCase). For a program of some tens of MB, linking takes several   
minutes. The CPU utilization is also very low during long periods of time. If 
the output is placed e.g. on /tmp, linking is several times faster. 
 
It is a bit hard to supply a good test case, however any large C++ program   
should give some insight. 
 
I have also run 'strace' on 'ld' and noticed a large number of _llseek() and   
write() calls for the output file. This dominates the number of system calls   
after a while, since the input files seem to be cached. Many writes also   
transfer a small amount of data.
Comment 1 Alan Modra 2019-11-22 04:15:32 UTC
I doubt anyone will ever do anything about this, sorry.