If you'd looked at the code, you'd see that it spends its entire time in a loop doing the same things -- reading from an input file and writing to many output files -- over and over.
The pause appears to occur when the cumulative affect of many writes to many output files exhausts the file cache buffers and it needs to flush them to disk en-masse before it can continue.
The intriguing thing was why this pregnant pause would only occur once, rather early in the run. The answer to that appears to be that the OS defers allocating disk extants to output files until it needs to flush the first write from the cache.
In reply to Re^2: Diagnosing a pregnant pause.
by BrowserUk
in thread Diagnosing a pregnant pause.
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |