Dear readers, 

Clues sought to the black arts of 3000 performance tuning. 

The queues on our 957 running approx 50 sessions and a handful
of batch processes is as follows.  In general we use CQ for 
true OLTP applications, DQ for batch jobs and EQ for online users
with cpu hungry applications. (Mainly to protect our CQ users)

We are increasing the number of hungry users all of the time and 
I have noticed that in some circumstances STORE type operations
will grind to a complete halt with our current set up. 

I need a compromise solution that will enable my online users 
to get sensible response times from their online reports but 
at the same time protects my high volume, low CPU OLTP users and
my background operations type tasks (stores and the like). 

I know that this is very limited information to go on but
will be happy to post more details if you can suggest solutions 
which work for you! 

                    ------QUANTUM-------
QUEUE  BASE  LIMIT  MIN    MAX    ACTUAL  BOOST  TIMESLICE
-----  ----  -----  ---    ---    ------  -----  ---------
 CQ    152    200   1      2000   18      DECAY    200
 DQ    202    238   2000   2000   2000    DECAY    200
 EQ    160    238   1      200    25      DECAY    200

I have tried oscillating the DQ and EQ but it seemed to make
things worse (fast performance for a period then nothing 
for several seconds)

All suggestions welcomed.

Thanks in advance

David Randall, IT Manager, Healthcall Services Limited 
401 South Row, Milton Keynes, Bucks.. MK9 2PH http:\\www.healthcall.co.uk
Voice +1908 691919 Fax : +1908 690169 mailto:\\[log in to unmask]