Le 14 févr. 08 à 02:22, Marion Hakanson a écrit :
> [EMAIL PROTECTED] said:
>> It's not that old. It's a Supermicro system with a 3ware 9650SE-8LP.
>> Open-E iSCSI-R3 DOM module. The system is plenty fast. I can pretty
>> handily pull 120MB/sec from it, and write at over 100MB/sec. It
>> f
[EMAIL PROTECTED] wrote:
On Tue, Feb 12, 2008 at 10:21:44PM -0800, Jonathan Loran wrote:
Thanks for any help anyone can offer.
I have faced similar problem (although not exactly the same) and was going to
monitor disk queue with dtrace but couldn't find any docs/urls about it.
Finally
On Tue, Feb 12, 2008 at 10:21:44PM -0800, Jonathan Loran wrote:
>
> Hi List,
>
> I'm wondering if one of you expert DTrace guru's can help me. I want to
> write a DTrace script to print out a a histogram of how long IO requests
> sit in the service queue. I can output the results with the qua
G'Day Jon,
On Thu, Feb 14, 2008 at 02:54:58PM -0800, Jonathan Loran wrote:
>
Hi Brendon,
I have been using iopending, though I'm not sure how to interpret it.
Is it true the column on the left is how deep in the queue requests are,
and then the histogram represents home many requests there are at each
queue depth? Then I would guess if there's lots of requests with h
G'Day Jon,
For disk layer metrics, you could try Disk/iopending from the DTraceToolkit
to check how saturated the disks become with requests (which answers that
question with much higher definition than iostat). I'd also run disktime.d,
which should be in the next DTraceToolkit release (it's pret
Marion Hakanson wrote:
[EMAIL PROTECTED] said:
It's not that old. It's a Supermicro system with a 3ware 9650SE-8LP.
Open-E iSCSI-R3 DOM module. The system is plenty fast. I can pretty
handily pull 120MB/sec from it, and write at over 100MB/sec. It falls apart
more on random I/O. The s
[EMAIL PROTECTED] said:
> It's not that old. It's a Supermicro system with a 3ware 9650SE-8LP.
> Open-E iSCSI-R3 DOM module. The system is plenty fast. I can pretty
> handily pull 120MB/sec from it, and write at over 100MB/sec. It falls apart
> more on random I/O. The server/initiator side is
Marion Hakanson wrote:
[EMAIL PROTECTED] said:
...
I know, I know, I should have gone with a JBOD setup, but it's too late for
that in this iteration of this server. We we set this up, I had the gear
already, and it's not in my budget to get new stuff right now.
What kind of arra
> Way crude, but effective enough:
kinda cool, but isn't thats what
sar -f /var/adm/sa/sa`date +%d` -A | grep -v ","
is for? crontab -e sys
to start..
for more fun
acctadm -e extended -f /var/adm/exacct/proc process
Rob
___
zfs-discu
[EMAIL PROTECTED] said:
> difference my tweaks are making. Basically, the problem users experience,
> when the load shoots up are huge latencies. An ls on a non-cached
> directory, which usually is instantaneous, will take 20, 30, 40 seconds or
> more. Then when the storage array catches up,
Hi List,
I'm wondering if one of you expert DTrace guru's can help me. I want to
write a DTrace script to print out a a histogram of how long IO requests
sit in the service queue. I can output the results with the quantize
method. I'm not sure which provider I should be using for this. Doe
12 matches
Mail list logo
