I tracked this problem down to a missing '--enable-maxmem=16' on the
./configure command line. The parameter specifies (in megabytes) the
maximum amount of main memory libjpeg should allocate before creating
backing store on disk; 8, 16 or 32 seem to be reasonable values for modern
hardware. And if you don't like it, you can always either set JPEGMEM
in the environment or use the -maxmemory command-line parameter.
Making this change has a huge impact on the usability of my linux 2.6.15
machine with 320M of main memory when dealing with huge (11M or so) JPEG
files. jpegtran is *much* faster (tested with -maxmemory=64m) with the
'ansi' memory manager and a limited main memory size than it was beofre
(with the 'nop' memory manager and >400M virtual memory allocated).
Because libjpeg is used throughout the system, I expect this will help fix
performance problems with large jpeg files throughout debian.
--scott
Panama JMMADD Dictionary Cocaine CABOUNCE supercomputer anthrax Bejing
GPFLOOR ESODIC BLUEBIRD Yakima Richard Tomlinson Boston Moscow Castro
( http://cscott.net/ )
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
