Not an expert on this, but googling "win32 performance counters" led me here: http://msdn.microsoft.com/en-us/library/aa373193(VS.85).aspx
Should let you get the available physical memory in the system. Not sure that you can specify to Windows that you want physical memory when you create the image objects, but it might be OK as a rough guide of whether there is memory available or not. Steven On Thu, Jan 29, 2009 at 1:32 PM, geoff <imageguy1...@gmail.com> wrote: > > There's no easy fix. Thumbnails and some kind of least-recently-used > > caching scheme are probably your best choices. As Steven pointed out, > > you could always install a Win64 system and a 64-bit Python. Then, you > > can get about 8TB of process space. However, that's not particularly > > friendly to your end users, if you need to distribute this. > > Not really and option as we do need to distribute and the users are > not at all 'power users' > > > No. The 2GB address space limit is per process. It doesn't matter what > > other processes are doing. You can even have several processes using > > 2GB of memory, although your disk will get a good workout. > > Thanks. > Any tips/hints on calculating the potentially available space ? > _______________________________________________ > python-win32 mailing list > python-win32@python.org > http://mail.python.org/mailman/listinfo/python-win32 >
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32