The dba tested on the two systems using NetApp/nSeries storage.
Both are AIX lpars
The QA system is AIX 7100-03
Host Utilities 6.0.0.0
QA Mounts for one of 25 databases - all mounts are the same
/dev/fslv148 /oracle/fnce20p/dbfiles jfs2 Jun 14 10:25
rw,cio,log=/dev/loglv50
/dev/fslv149 /oracle/fnce20p/temp jfs2 Jun 14 10:25
rw,cio,log=/dev/loglv50
/dev/fslv144 /oracle/fnce20p/logs1 jfs2 Jun 14 10:25
rw,cio,log=/dev/loglv49
/dev/fslv145 /oracle/fnce20p/logs2 jfs2 Jun 14 10:25
rw,cio,log=/dev/loglv49
/dev/fslv146 /oracle/fnce20p/archive jfs2 Jun 14 10:25
rw,log=/dev/loglv49
/dev/fslv147 /oracle/fnce20p/dump jfs2 Jun 14 10:25
rw,log=/dev/loglv49
/dev/ramdisk0 /oracle/fnce20p/tempram jfs2 Jun 22 06:05
rw,cio,log=INLINE
One /etc/filesystems entry - all are the same
/oracle/fnce20p/dbfiles:
dev = /dev/fslv148
vfs = jfs2
log = /dev/loglv50
mount = true
check = false
options = rw,cio
account = false
The Prod system is AIX 6100-08
Host Utilities 6.0.0.0
Prod Mounts for one of 25 databases - all mounts are the same
/dev/fslv148 /oracle/fnce20p/dbfiles jfs2 Jun 28 20:30
rw,cio,log=/dev/loglv50
/dev/fslv147 /oracle/fnce20p/dump jfs2 Jun 28 20:30
rw,log=/dev/loglv49
/dev/fslv149 /oracle/fnce20p/temp jfs2 Jun 28 20:30
rw,cio,log=/dev/loglv50
/dev/fslv145 /oracle/fnce20p/logs2 jfs2 Jun 28 20:30
rw,cio,log=/dev/loglv49
/dev/fslv146 /oracle/fnce20p/archive jfs2 Jun 28 20:30
rw,log=/dev/loglv49
/dev/fslv144 /oracle/fnce20p/logs1 jfs2 Jun 28 20:30
rw,cio,log=/dev/loglv49
One /etc/filesystems entry - all are the same.
Mount is "false" due to this being a Veritas VCS cluster.
/oracle/fnce20p/dbfiles:
dev = /dev/fslv148
vfs = jfs2
log = /dev/loglv50
mount = false
check = false
options = rw,cio
account = false
From: jordan slingerland [mailto:jordan.slingerland AT gmail DOT com]
Sent: Wednesday, June 29, 2016 8:30 PM
To: Rhodes, Richard L. <rrhodes AT firstenergycorp DOT com>
Cc: toasters AT teaparty DOT net
Subject: Re: OnTap read block size?
Please post the mount line from /etc/fstab or /etc/filesystems etc along with
client os version
On Jun 29, 2016 10:44 AM, "Rhodes, Richard L." <rrhodes AT firstenergycorp DOT
com<mailto:rrhodes AT firstenergycorp DOT com>> wrote:
OnTap 8.1.2p1
Our DBA's are complaining that our nSeries (N3220/FAS2240) is reading really
slow due to it only returning small 16k blocks. The DBA's are saying the
Oracle multi-block read ahead should be reading 128 x 16k blocks = 2m read, but
it's only seems to be reading/returning 16k at a time.
On a AIX filesystem mounted CIO, if I run
"dd if=/dev/zero of=z bs=1m count=9999"
I see writes of 500k.
In the same filesystem mounted CIO, if I read an existing db file
"dd if=<dbfile> of=/dev/null bs=1m"
I see reads of up to 30k.
Q) Is there a limit in OnTap on read size?
Thanks
Rick
________________________________
________________________________
The information contained in this message is intended only for the personal and
confidential use of the recipient(s) named above. If the reader of this message
is not the intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify us immediately, and delete the original message.
_______________________________________________
Toasters mailing list
Toasters AT teaparty DOT net<mailto:Toasters AT teaparty DOT net>
http://www.teaparty.net/mailman/listinfo/toasters
-----------------------------------------
The information contained in this message is intended only for the personal and
confidential use of the recipient(s) named above. If the reader of this message
is not the intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify us immediately, and delete the original message.
|