before turning on auto-tuner:
wrkshrpool
is everything running out of *base and is there
adequate min/max for the pool? or, is the db
activity running in a shared pool?
you can see where it is running by doing:
wrkactjob F11
look for the pool ID
you might also run idoctor against the system
to get a clearer understanding of where the
performance troubles are coming from.
also, are you using toolkit or native driver for
sql access? this can impact performance too.
as for processors, there are 400 models that have
single processor (maybe this is a 270?) as well as
models that exceed 20+ processors.
-slugbug