AS/400 performance, CPU at 40%

AS/400 administration
AS/400 performance
CPU usage
what can be wrong when the system is slow and is only taking up 40% CPU

Software/Hardware used:

Answer Wiki

Thanks. We'll let you know when a new response is added.

% CPU utilizada . . . . : 28,5 Armazenamento auxiliar:
% função de BD . . . . . : 26,3 ASP do sistema . . . . : 6139 G
Tempo decorrido . . . . : 00:00:38 % ASP do sist.utilizado: 54,5064
Trabalhos no sistema . . : 9377 Total . . . . . . . . : 6139 G
% endereços perm . . . . : 0,312 Desprot. actual utlzda : 43988 M
% endereços temp . . . . : 16,107 Desprotecção máxima . : 52400 M

Escreva as alterações (se for permitido), prima Enter.

Conj. Tamanho Tamanho Máx —–BD—– —Não BD—
sist. conj. (M) rsrvd (M) activo Falha Págs Falha Págs
1 16014,6 1776,4 +++++ 0,0 0,0 0,0 0,0
2 60960,8 44,1 1440 46,6 5336 44,7 204,1
3 12472,3 3,3 200 1,6 3844 18,2 96,6
4 11366,8 0,0 300 14,6 33,7 3,3 8,5
5 1018,3 0,0 11 0,0 0,0 0,0 0,0

Discuss This Question: 10  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Aringarosa
    Are the disks OK?
    335 pointsBadges:
  • Gabe9527
    Memory OK? You need to look at the alocation to the SYSTEM as you mght have allocated to much resource to the Applications....
    11,095 pointsBadges:
  • RicardoPereira
    Memory seems to me good and disks well
    30 pointsBadges:
  • TomLiotta
    what can be wrong when the system is slow Lots of things could be wrong. Or nothing could be wrong. There's no way for us to tell. First, what is meant by "system is slow"? Slow interactive response time? Slow database access from remote clients? Slow batch jobs? Slow subsystem startup? All of those? Something else? What is considered 'slow'? Has it always been 'slow'? If not, how has it changed and over what period of time? and is only taking up 40% CPU Over how much time? The interval shown ("Tempo decorrido") was only 00:00:38 seconds. Usually, a meaningful value requires at the least 5 minutes and should probably be as much as 15 minutes. The interval should cover a time when the work being done is representative of the work being measured. Also, without knowing anything about the type of work being done, there's no way to know if 40% is poor or even very, very good. It looks as if the system is only using five system memory pools. It's impossible to be certain if system pool 3 or 4 is the *INTERACT shared pool and what the one that isn't *INTERACT is. Regardless, with 100GB of memory and only five system pools, it's likely that no one has done much, if any, configuration to allow measurements of performance. If the system is running under the general default work management configuration, then it should be configured to get the various types of work into their separate memory pools. Once that's done, it becomes far easier to see where problems might be (if any exist). Naturally, any basic problems, e.g., DASD cache batteries, etc., should be eliminated before anything else is done. Tom
    125,585 pointsBadges:
  • Yorkshireman
    As Tom says (paraphrasing) - 'define slow' Start by emailing all users, asking them to tell you. or diarise, over a week, whenever they 'think' the system is slow, and what they were doing. That gives you something to investigate, and may eliminate, or identify, 'wildcard users' who can be discarded, or who listened to. For the periods at issue, turn on some diagnostics - telling people that for a week, you wil lbe running monitoring software (which has an impact) Sit down with a coffee and the stats, and see if there are jobs which are badly behaved. Spot wherte peaks of activity accorr and track back to what the system was doing. Oh - and set a level of expectation among users - such as 'response times under 5 seconds are acceptable' - or maybe 'we are investigating, so please only report response times over 10 seconds for the next week, and we will be working on ones over 5 seconds next month when the first round is fixed' Oh Oh - adding a status message ' the system is processing records xxxxxx remaining' is a good way of killing impatience when a user initiates processes over large files - I leave you to engineer a way of passing back a message from a running program containing the record count.
    6,085 pointsBadges:
    If you have MPG - Performance Navigator, use the graphs. Also, TAATOOLS have some good commands for this.
    3,175 pointsBadges:
  • TomLiotta
    If you have MPG - Performance Navigator, use the graphs. Also, TAATOOLS have some good commands for this. Be aware that performance measurements can be very misleading if reasonable work management configuration hasn't been started yet. Simple performance adjuster settings (QPFRADJ) shouldn't even be enabled until after work management is configured -- it will often make things worse. Tom
    125,585 pointsBadges:
  • Abigail
    40% utilization may seem low, but depending on the type of activity is understandable. I would recommend: WRKACTJOB Place your curser on the CPU% and press F16. This will sort the utilization by high to low. Look at what is taking the high utilization. These types of jobs may need priority/timeslice adjustments. File indexing functions could be your issue. If the 40% is interactive utilization, depending on the function, performance could be adversely affected. Hope this may help you in determining your issue. Kim K.
    645 pointsBadges:
  • OldSysAdmin
    You can also use Ops Nav (now called System i Navigator) to set up monitors on average CPU Utilization with a 15 second refresh to monitor what jobs are running and how much CPU they're using (there's many other monitors available that might be helpful). Expand Manegement Central, Monitors, System and experiment.
    945 pointsBadges:
  • as400systemadministratordefine
    i think must see in sysopr msgs, ANY Msgs(ERROR) that need to reply displayed in it or not,that also may be one of the reason... Eshwarbose
    40 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: