[gs-bugs] [Bug 689534] Poor performance reading PDF file

bugs.ghostscript.com-bugzilla-daemon at ghostscript.com bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
Mon Apr 28 10:06:37 PDT 2008


ray.johnston at artifex.com changed:

           What    |Removed                     |Added
                 CC|                            |leonardo at artifex.com

------- Additional Comments From ray.johnston at artifex.com  2008-04-28 10:06 -------
On my Intel Core 2 Duo processor, using the following parameters:

gswin32c -sDEVICE=tiff24nc -r300 -o nul -dBufferSpace=32000000 -Z: -q -c
32000000 setvmthreshold -f 689534.pdf

I see 42 seconds parse time, then 272 sec total time.

A problem exists in the clist logic since the memory at render time is supposed
to be fairly 'fixed' (only high-level paths cause temporary growth), but
watching the memory usage (Task Manager on Windwos, 'top' on linux) I see that
the total memory used is about 100K bytes at start of rendering, but GROWS 
gradually as the rendering progresses to > 580k bytes before the page is done.

This may be a memory leak in the clist/graphics library. I will collect more
information about the memory use during each band.

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the gs-bugs mailing list