***UNCHECKED*** Re: ASM Filter Driver Performance

From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 26 Jan 2018 08:11:59 -0800
Message-ID: <CAORjz=MOsgKnjkYr32YjuZepuzXuzC=Q7=2LAkesFseOrGhc8w_at_mail.gmail.com>



Hi Niall, comments inline:

On Fri, Jan 26, 2018 at 3:45 AM, Niall Litchfield < niall.litchfield_at_gmail.com> wrote:

> Hi Jared
>
> The AWR reports look a little odd to me. I'd expect a SLOB Update test to
> result in write I/O as well as read I/O. For comparison here's an output
> from a 25% update run I did recently.
>
>
Agreed. I suspect it may be an AWR report bug.

Collecting AWR metrics at the PDB level is new to 12.2, and there may be bugs.

What I have planned to do is run another test but manually run AWR before/after snapshots at the CDB level and then run that report.

> So far as I can tell there's no write activity in your AWR reports. I'd
> further suggest that a useful metric since you are looking at I/O
> performance, would be SLOBOps/sec/vCPU - or else duration of a fixed run.
>
>
Agreed, not much in the report, but as SLOB was always set to 20-50% update, there definitely should be write activity.

> That all said, I see you are using the current (or at least a recent)
> version of slob, whereas I'm still using one from 2014 (not yet validated
> comparability of results from the newer kit).
>

Yes, the most recent version of SLOB.

I have modified it a bit to call the AWR reports at the PDB level. These are minor changes to call PDB rather than CDB reports.

Seen here if you like: https://github.com/jkstill/SLOB-PDB

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/ Github: https://github.com/jkstill

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jan 26 2018 - 17:11:59 CET

Original text of this message