If you move QHTTPSVR subsystem and it's jobs into a shared memory pool, make sure to move the ZendSvr subsystem into that same memory. The Zend server uses memory in very specific ways that make the two sets of jobs need to run in the same memory.

I think that is a very good thing to do, but they have to go together.

As far as the shared pools vs. fixed memory pool, stay with a shared pools and set the paging option to *CALC. Threads will be about 200 to start depending on how many Apache servers are running.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 8/13/13 9:03 AM, Michael Ryan wrote:
Hi folks -

Implementing a PHP solution on an E6C system. Lots of memory, lots of disk,
system isn't overworked at this point. V7R1. System value QPFRADJ is set to
3 (Automatic Adjustment). Default Zend Server 6 installation uses *BASE
memory pool.

Zend Server performance is lousy. Much slower page load and data retrieval
than the same code on the development system. Lots of Toolkit and stored
procedure use.

I'm thinking that the first step would be to establish a fixed memory pool
just for Zend Server, set it to *NOMAX for threads, and see how it runs.

What tuning recommendations, for both Apache and Zend, do you folks
suggest? Any good documentation on this?

Thanks!
--


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-2019 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].