Re: Subsystem and Apache Setup for Zend Server 6

Jim - I set up a new *SHRPOOL entry and changed the ZENDSVR6 subsystem to
use that shared pool:

Subsystem description: ZENDSVR6 Status: ACTIVE

Pool Storage Activity
ID Size (K) Level
1 *SHRPOOL6

Are you saying that I should change the QHTTPSVR subsystem to use the same
shared pool? And that I should change the Activity Level for the pool
definition in the SBSD to 200?

Thanks!


On Tue, Aug 13, 2013 at 1:26 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

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 is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.