It is definitely defined in b63... not sure when it got introduced.
http://src.opensolaris.org/source/xref/onnv/aside/usr/src/cmd/mdb/common/modules/zfs/zfs.c
shows tunable parameters for ZFS, under "zfs_params(...)"
On 5/20/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
Marko Milisavljevic wr
Marko Milisavljevic wrote:
Thank you, following your suggestion improves things - reading a ZFS
file from a RAID-0 pair now gives me 95MB/sec - about the same as from
/dev/dsk. What I find surprising is that reading from RAID-1 2-drive
zpool gives me only 56MB/s - I imagined it would be roughly l
Thank you, following your suggestion improves things - reading a ZFS
file from a RAID-0 pair now gives me 95MB/sec - about the same as from
/dev/dsk. What I find surprising is that reading from RAID-1 2-drive
zpool gives me only 56MB/s - I imagined it would be roughly like
reading from RAID-0. I c
Marko,
Matt and I discussed this offline some more and he had a couple of ideas
about double-checking your hardware.
It looks like your controller (or disks, maybe?) is having trouble with
multiple simultaneous I/Os to the same disk. It looks like prefetch
aggravates this problem.
When I asked M
At Matt's request, I did some further experiments and have found that
this appears to be particular to your hardware. This is not a general
32-bit problem. I re-ran this experiment on a 1-disk pool using a 32
and 64-bit kernel. I got identical results:
64-bit
==
$ /usr/bin/time dd if=/test
I will do that, but I'll do a couple of things first, to try to isolate the
problem more precisely:
- Use ZFS on a plain PATA drive on onboard IDE connector to see if it works
with prefetch on this 32-bit machine.
- Use this PCI-SATA card in a 64-bit, 2g RAM machine and see how it performs
there,
Marko Milisavljevic wrote:
now lets try:
set zfs:zfs_prefetch_disable=1
bingo!
r/sw/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
609.00.0 77910.00.0 0.0 0.80.01.4 0 83 c0d0
only 1-2 % slower then dd from /dev/dsk. Do you think this is general
32-bit probl
Marko Milisavljevic wrote:
Got excited too quickly on one thing... reading single zfs file does
give me almost same speed as dd /dev/dsk... around 78MB/s... however,
creating a 2-drive stripe, still doesn't perform as well as it ought to:
Yes, that makes sense. Because prefetch is disabled, Z
Got excited too quickly on one thing... reading single zfs file does give me
almost same speed as dd /dev/dsk... around 78MB/s... however, creating a
2-drive stripe, still doesn't perform as well as it ought to:
r/sw/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
294.30.0 3767
Hello Matthew,
Yes, my machine is 32-bit, with 1.5G of RAM.
-bash-3.00# echo ::memstat | mdb -k
Page SummaryPagesMB %Tot
Kernel 123249 481 32%
Anon
Marko Milisavljevic wrote:
I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can
deliver from a drive, and doing this: dd if=(raw disk) of=/dev/null gives
me around 80MB/s, while dd if=(file on ZFS) of=/dev/null gives me only
35MB/s!?.
Our experience is that ZFS gets very clos
Marko Milisavljevic wrote:
I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can deliver
from a drive, and doing this:
dd if=(raw disk) of=/dev/null gives me around 80MB/s, while dd if=(file on ZFS)
of=/dev/null gives me only 35MB/s!?. I am getting basically the same result
w
On Mon, 14 May 2007, Marko Milisavljevic wrote:
[ ... reformatted ]
> I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can
> deliver from a drive, and doing this: dd if=(raw disk) of=/dev/null
> gives me around 80MB/s, while dd if=(file on ZFS) of=/dev/null gives me
> only 3
I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can deliver
from a drive, and doing this:
dd if=(raw disk) of=/dev/null gives me around 80MB/s, while dd if=(file on ZFS)
of=/dev/null gives me only 35MB/s!?. I am getting basically the same result
whether it is single zfs drive
14 matches
Mail list logo
