Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
A user reported users complaining of a slow IDS instance (9.4 on AIX 5) and posted onstat -p output showing 0% read cache, huge sequential scan counts and many bufwaits, asking what else besides UPDATE STATISTICS could be tuned. Responders noted the figures were cumulative since a long uptime and essentially meaningless, so he should run onstat -z and review again after a full day's processing; they also said MEDIUM-level statistics are usually insufficient (use the Performance Guide method or Art Kagel's dostats), and suggested checking online.log for restarts, config or kernel parameter changes, with the 0% cache pointing to an application doing huge table scans. The poster zeroed the counters and said he would monitor; no final outcome is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
you need to run onstat -p again. 0.00 for the read cache is about as bad
as it gets. Also the sequential scans look really bad, so I gotta ask
about your statistics.
M.P.
From: "JACK PAPA" <informix2009@gmail.com>
To: ids@iiug.org
Date: 08/03/2011 09:19 PM
Subject: How to check what/where is the culprit of slowdown [24527]
Sent by: ids-bounces@iiug.org
Hi All,
My users are complaining that my IDS is slow. Update statistics is less
than a
week ago. onstat -p shows Disk Read/Disk Write below:
------------------
Profile
dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached
2247456978 3351759488 735188490 0.00 656580507 1052080848 917352482 28.43
isamtot open start read write rewrite delete commit rollbk
3087700866 4004612940 4292605915 4288949939 1110721655 290580190 245838728
421992778 233348
gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs
0 0 0 0 0 0 0
ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes
0 0 0 4867662.44 663059.78 9958 19916
bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
251655930 52741 2531693371 30 0 60671 82941606 609114571
ixda-RA idx-RA da-RA RA-pgsused lchwaits
406028401 99021526 658213131 1149780329 94770852
------------------------
Is there any other way to tune up IDS other than update stats?
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Jack,
Zero out the stats and review them again after a full day of processing.
These numbered don't make much sense. Version? Platform? Uptime?
Art
On Aug 3, 2011 10:19 PM, "JACK PAPA" <informix2009@gmail.com> wrote:
> Hi All,
>
> My users are complaining that my IDS is slow. Update statistics is less
than a
> week ago. onstat -p shows Disk Read/Disk Write below:
>
> ------------------
> Profile
> dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached
> 2247456978 3351759488 735188490 0.00 656580507 1052080848 917352482 28.43
>
> isamtot open start read write rewrite delete commit rollbk
> 3087700866 4004612940 4292605915 4288949939 1110721655 290580190 245838728
> 421992778 233348
>
> gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs
> 0 0 0 0 0 0 0
>
> ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes
> 0 0 0 4867662.44 663059.78 9958 19916
>
> bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
> 251655930 52741 2531693371 30 0 60671 82941606 609114571
>
> ixda-RA idx-RA da-RA RA-pgsused lchwaits
> 406028401 99021526 658213131 1149780329 94770852
>
> ------------------------
>
> Is there any other way to tune up IDS other than update stats?
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
--bcaec51b9a4910567b04a9a518bc
Medium is not usually good enough. Implement the recommendation in the
Performance Guide or just get my dostats utility and use that.
Art
Art
On Aug 3, 2011 10:53 PM, "JACK PAPA" <informix2009@gmail.com> wrote:
> Is it fine to re-execute onstat -z? to clear the benchmark?... The update
> stats is Medium and it was executed 07-30-2011.
>
> 07/30/2011 M
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
--20cf307cffd6b6a5fa04a9a52540
Thanks Art/Madison.
I had zeroed out benchmark. i'm running on version 9.4 on AIX 5(not supported
anymore). looks like the io is not 0 anymore after onstat -z.
i'll monitor until tomorrow if anything will be ok.
thanks your for your inputs.
Hi,
just to be sure ... I would check the online.log
message file to see, when the server was
restarted the last time and whether at that
time it reported any change of a config
parameter. If there was a restart, but no
change in config parameter, then check if
the restart coincides with a system reboot.
If that's the case check for changed kernel
parameters.
Other than that it is difficult to say much as
we don't know anything about performance
before users started complaining. But 0%
cached for reads really looks very bad.
If that is true I'd say there should be a
rampant application doing overly large
table scans ...
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
Read about the Informix Warehouse Accelerator:
http://tinyurl.com/the-iwa-blog
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 08/04/2011 04:18:54 AM:
>
> Hi All,
>
> My users are complaining that my IDS is slow. Update statistics is less
than a
> week ago. onstat -p shows Disk Read/Disk Write below:
>
> ------------------
> Profile
> dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached
> 2247456978 3351759488 735188490 0.00 656580507 1052080848 917352482
28.43
>
> isamtot open start read write rewrite delete commit rollbk
> 3087700866 4004612940 4292605915 4288949939 1110721655 290580190
245838728
> 421992778 233348
>
> gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs
> 0 0 0 0 0 0 0
>
> ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes
> 0 0 0 4867662.44 663059.78 9958 19916
>
> bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
> 251655930 52741 2531693371 30 0 60671 82941606 609114571
>
> ixda-RA idx-RA da-RA RA-pgsused lchwaits
> 406028401 99021526 658213131 1149780329 94770852
>
> ------------------------
>
> Is there any other way to tune up IDS other than update stats?
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.