On Thu, 2009-03-05 at 04:41 +1100, Ken McDonell wrote:
> This one is totally CPU bound ... it used to run for 220-odd seconds on
> my clunker workstation (I've no idea what Nathan's using to stretch that
> to 800+ seconds), and I can get it down to 70-odd seconds with a couple
> of quick optimizations ... but it is exploring 4096 cases (considering
> each word-aligned truncation of the last 16K bytes of the archive to
> mimic what might happen with aborted stdio buffering of the output from
> pmlogger) for each of 3 archives, and without remembering exactly what
> triggered the problem in the past, I'm not sure I can make it do less
> work without changing the test coverage.
S'okay - knowing now its meant to be cpu bound, I looked closer and
found it was spending alot of time in I/O wait (possibly due to the
truncates) ... a few tweaks to my system and its CPU bound here too
now, and runs in 2mins on my (single cpu) pentium4.
thanks.
--
Nathan
|