Bug#346023: more information

2006-05-03 Thread C. Scott Ananian
On Wed, 3 May 2006, Bill Allombert wrote: So I am considering following Guido advice and set the default value to 1024M (so JPEGMEM still work but the 'nop' memory manager is almost always used). However I am surprised the speed differences are so large, it looks like the ansi allocator is very

Bug#346023: more information

2006-05-03 Thread Bill Allombert
On Wed, Jan 04, 2006 at 08:06:20PM -0500, C. Scott Ananian wrote: > 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

Bug#346023: more information

2006-01-24 Thread C. Scott Ananian
On Tue, 24 Jan 2006, Bill Allombert wrote: Hello Scott, I have made various checks and consulted with upstream, and I have no objection to add enable-maxmem. The only issue is to decide the default value, but 16 seems reasonable. Opinions ? Works for me. The other option would be to actually

Bug#346023: more information

2006-01-24 Thread Bill Allombert
On Wed, Jan 04, 2006 at 08:06:20PM -0500, C. Scott Ananian wrote: > 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

Bug#346023: more information

2006-01-04 Thread C. Scott Ananian
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.