If this IS the problem, you can lessen it by giving the jobs a bigger pool, maybe. It's part of the way the system works - jobs that are not doing anything are eligible to have their resources paged out so other jobs can get at the memory.

I don't know about multiple jobs running - I do remember seeing some stuff I found odd when working with the Apache server, not Zend, when I specified the number of CGI jobs to start for an instance - it doubled them up. But it's not your situation, so far as I can tell.

Vern

On 7/8/2010 10:24 AM, MattLavinder@xxxxxxxxxxxxxxxxxxx wrote:
Just a shot in the dark - there is the old least-most-recently-used
problem, where job assets have been paged out to disk and have to be
brought back in. This behavior smells like that.
Thanks- I don't suppose there is a way to verify or control this?

Also, still wondering about the number of jobs running. When I start up
the ZENDSVR jobs I see fewer jobs running than when I start my development
server. Have no idea why there are more jobs running because it appears
the FastCGI settings are the same. Any ideas?

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.