b_gilmore
Well Known Member
Re: [AS400 Performance Upgrade]
We went from a 2way to a 4way on an 820 just before go-live but didn't really
get a good feel for performance pre-golive as a comparable baseline. However
our package build times dropped from 5 hours client and server to 4 hours just
by adding the processors.
We run about 125 current users on 9 terminal server + XPI + data collection
with heave SOE, and most BSFNs mapped to the AS/400.
I found that tweaking the INI can make a lot of difference in response times
(e.g. opening up the Network and CallObject Kernel jobs). I run about a 2 to
1 ratio of CallObject Kernels to Network jobs.
Each JDENETn handles about 4 users and each JDE CallObject Kernel handles
about 2 to 3 users at the same time.
Additionally, you might look at running the JDE purge programs for audit files
that have become overgrown. You could also regenerate the indexes in
Production and run RCLPFM / RCLSTG. This kind of housekeeping could move you
back into acceptable ranges.
tdf <[email protected]> wrote:
along with adding 4 additional gig memory totalling 10gb. We have been
experiencing response time problems when the batch processing load increases.
We usually have 150 users active at peak time on 5 citrix servers. We have
been live for year. I am looking to find anyone with similiar experience who
have made the transition from a 2-way to 4-way. Did you find it worth the
money?
We went from a 2way to a 4way on an 820 just before go-live but didn't really
get a good feel for performance pre-golive as a comparable baseline. However
our package build times dropped from 5 hours client and server to 4 hours just
by adding the processors.
We run about 125 current users on 9 terminal server + XPI + data collection
with heave SOE, and most BSFNs mapped to the AS/400.
I found that tweaking the INI can make a lot of difference in response times
(e.g. opening up the Network and CallObject Kernel jobs). I run about a 2 to
1 ratio of CallObject Kernels to Network jobs.
Each JDENETn handles about 4 users and each JDE CallObject Kernel handles
about 2 to 3 users at the same time.
Additionally, you might look at running the JDE purge programs for audit files
that have become overgrown. You could also regenerate the indexes in
Production and run RCLPFM / RCLSTG. This kind of housekeeping could move you
back into acceptable ranges.
tdf <[email protected]> wrote:
along with adding 4 additional gig memory totalling 10gb. We have been
experiencing response time problems when the batch processing load increases.
We usually have 150 users active at peak time on 5 citrix servers. We have
been live for year. I am looking to find anyone with similiar experience who
have made the transition from a 2-way to 4-way. Did you find it worth the
money?
