Re: ASM of any significant value when switching to Direct NFS / NetApp / non-RAC?
From: Matthew Zito <matt_at_crackpotideas.com>
Date: Wed, 15 Aug 2012 22:04:25 -0400
Message-ID: <CAJ7936w6vnOH0a_5FxXdC=XFp1th_asOkRZP2Y_0Gs32yteBSg_at_mail.gmail.com>
You could do this with tcpdump/snoop/whatever packet sniffing technology you want, and then load it into wireshark. That should be sufficient to see the latency times packet-wise.
Date: Wed, 15 Aug 2012 22:04:25 -0400
Message-ID: <CAJ7936w6vnOH0a_5FxXdC=XFp1th_asOkRZP2Y_0Gs32yteBSg_at_mail.gmail.com>
You could do this with tcpdump/snoop/whatever packet sniffing technology you want, and then load it into wireshark. That should be sufficient to see the latency times packet-wise.
Not as clean or elegant as a v$ table or iostat, but you can get the data.
Matt
On Wed, Aug 15, 2012 at 4:51 PM, Austin Hackett <hacketta_57_at_me.com> wrote:
> Hi Dana
> This info doesn't exactly relate to ASM, but I hopefully it'll be of
> use to you in the future...
>
> I've recently started a new role at shop that uses Linux, Direct NFS
> and NetApp (no ASM) and as others have suggested, the solution does
> have a number of nice management features.
>
> However, I am finding the apparent lack of read and write latency
> stats frustrating.
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 15 2012 - 21:04:25 CDT