On Fri, 2009-02-20 at 10:55 +0100, Duncan Webb wrote: > I did notice that all the images are cached for later use but didn't > check when they are freed from the cache. Of course caching big images > would cause a memory problem.
kaa.imlib2 has two layers of cache: one for uncompressed data (16MB), and the one built into imlib2 for compressed data (4MB). The uncompressed data cache can be tuned: kaa.imlib2._image_cache['max-size'] = <number of bytes> Now that I look at the code, max-size is a bit of a lie. It will actually cache one image, even if that image exceeds the max size. So an extremely large image (3072x2048 in your example) will actually use an extra 24MB of memory. You can, however, bypass the uncompressed image cache by using kaa.imlib2.open_without_cache() > It should be a lot faster too, it takes quite a long time for imlib2 to > process a large photo (3072x2048) about 1.5 secs on my P3 box which is a > performance killer. beacon uses epeg (which is nowadays merged with evas, but beacon still has it split out), which is probably the fastest JPEG thumbnailer around. Jason. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
