On Nov 30, 2007, at 8:36 AM, Alexander Cohen wrote:
In that case, maybe you have an idea for me. I have a daemon that
runs and indexes all the images on a system. For each image, it
needs to open it up, get some info, close it and store that info.
This is very CPU consuming and can pretty much bring the system to
a halt after a while.
That doesn't seem right. Your daemon shouldn't be able to monopolize
the CPU. Are you sure that's what's going on?
I wonder if what is really happening is that you're memory usage is
getting out of hand and causing virtual memory thrashing.
