[J3] [EXTERNAL] [BULK] Re: Question to compiler developers about compilation speed
Clune, Thomas L. (GSFC-6101)
thomas.l.clune at nasa.gov
Tue Nov 5 15:01:30 UTC 2024
We have now benchmarked compiling very small files, and found that it is generally << 10% of the time spent compiling “real” code. So mere file access does not seem to be a major contributor to what we are seeing.
From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Van Snyder via J3 <j3 at mailman.j3-fortran.org>
Date: Wednesday, October 30, 2024 at 1:06 PM
To: j3 at mailman.j3-fortran.org <j3 at mailman.j3-fortran.org>
Cc: Van Snyder <van.snyder at sbcglobal.net>
Subject: Re: [J3] [EXTERNAL] [BULK] Re: Question to compiler developers about compilation speed
CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.
On Wed, 2024-10-30 at 15:15 +0000, Clune, Thomas L. (GSFC-6101) via J3 wrote:
Again – one of the first things we tried was to place all of the source files and TMPDIR onto SSD and we saw very little change in performance.
This suggests that I/O is not the bottleneck, unless it is metadata contention on our shared filesystem. I would think the latter would also be small because we are not talking about lots of files here in the grand scheme and metadata access ought to be 2-3 orders of magnitude faster than what we are seeing. I suppose if the compiler is opening and closing the same file over and over again then metadata might be the culprit.
I don't know what the situation is now, but many years ago, opening and closing a small file was much more time consuming than reading it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20241105/19751f26/attachment.htm>
More information about the J3
mailing list