Apologies for cross posting but I have been looking at the probes fired when a
snapshot is created.
I get
pa...@openindiana:~/programming/dtrace$ pfexec ./snapshots.d
dtrace: script './snapshots.d' matched 54 probes
CPU IDFUNCTION:NAME
0 37478 zfs_secpolicy_snapshot
On Thu, 7 May 2009, Moore, Joe wrote:
Carson Gaspar wrote:
Not true. The script is simply not intelligent enough. There are really
3 broad kinds of RAM usage:
A) Unused
B) Unfreeable by the kernel (normal process memory)
C) Freeable by the kernel (buffer cache, ARC, etc.)
Monitoring usually s
Carson Gaspar wrote:
> Not true. The script is simply not intelligent enough. There are really
> 3 broad kinds of RAM usage:
>
> A) Unused
> B) Unfreeable by the kernel (normal process memory)
> C) Freeable by the kernel (buffer cache, ARC, etc.)
>
> Monitoring usually should focus on keeping (A+
Fajar A. Nugraha wrote:
On Wed, May 6, 2009 at 10:17 PM, Richard Elling
wrote:
Fajar A. Nugraha wrote:
IMHO it's probably best to set a limit on ARC size and treat it like
any other memory used by applications.
There are a few cases where this makes sense, but not many.
On Wed, May 6, 2009 at 10:17 PM, Richard Elling
wrote:
> Fajar A. Nugraha wrote:
>> IMHO it's probably best to set a limit on ARC size and treat it like
>> any other memory used by applications.
>>
>
> There are a few cases where this makes sense, but not many. The ARC
> will shrink, as needed.
Bob Friesenhahn wrote:
It seems like this Nagios script is not very useful since the notion of
"free memory" has become antiquated.
Not true. The script is simply not intelligent enough. There are really
3 broad kinds of RAM usage:
A) Unused
B) Unfreeable by the kernel (normal process memor
Ben Rockwood's written a very useful util called arc_summary:
http://www.cuddletech.com/blog/pivot/entry.php?id=979
It's really good for looking at ARC usage (including memory usage).
You might be able to make some guesses based on "kstat -n zfs_file_data"
and "kstat -n zfs_file_data_buf". Look
On Wed, 6 May 2009, Richard Elling wrote:
Memory is meant to be used. 96% RAM use is good since it represents an
effective use of your investment.
Actually, I think a percentage of RAM is a bogus metric to measure.
For example, on a 2TBytes system, you would be wasting 80 GBytes.
Perhaps you
Bob Friesenhahn wrote:
On Wed, 6 May 2009, Troy Nancarrow (MEL) wrote:
Please forgive me if my searching-fu has failed me in this case, but
I've been unable to find any information on how people are going about
monitoring and alerting regarding memory usage on Solaris hosts using
ZFS.
The pr
On Wed, 6 May 2009, Troy Nancarrow (MEL) wrote:
Please forgive me if my searching-fu has failed me in this case, but
I've been unable to find any information on how people are going about
monitoring and alerting regarding memory usage on Solaris hosts using
ZFS.
The problem is not that the ZFS
Fajar A. Nugraha wrote:
On Wed, May 6, 2009 at 1:08 PM, Troy Nancarrow (MEL)
wrote:
So how are others monitoring memory usage on ZFS servers?
I think you can get the amount of memory zfs arc uses with arcstat.pl.
http://www.solarisinternals.com/wiki/index.php/Arcstat
arcstat is a
Troy Nancarrow (MEL) schrieb:
> Hi,
>
> Please forgive me if my searching-fu has failed me in this case, but
> I've been unable to find any information on how people are going about
> monitoring and alerting regarding memory usage on Solaris hosts using ZFS.
>
> The problem is not that the ZFS
On Wed, May 6, 2009 at 1:08 PM, Troy Nancarrow (MEL)
wrote:
> So how are others monitoring memory usage on ZFS servers?
I think you can get the amount of memory zfs arc uses with arcstat.pl.
http://www.solarisinternals.com/wiki/index.php/Arcstat
IMHO it's probably best to set a limit on ARC size
Hi,
Please forgive me if my searching-fu has failed me in this case, but
I've been unable to find any information on how people are going about
monitoring and alerting regarding memory usage on Solaris hosts using
ZFS.
The problem is not that the ZFS ARC is using up the memory, but that the
scr
By combining two great tools arcstat and dimstat you can get ZFS statistics in:
* table view
* chart view
* any date/time interval
* host to host compare
For example, online table and chart view
Ream more here
http://blogs.sun.com/pomah/entry/monitoring_zfs_statistic
--
This mes
Hello Neil,
Wednesday, December 13, 2006, 1:59:15 AM, you wrote:
NP> Tom Duell wrote On 12/12/06 17:11,:
>> Group,
>>
>> We are running a benchmark with 4000 users
>> simulating a hospital management system
>> running on Solaris 10 6/06 on USIV+ based
>> SunFire 6900 with 6540 storage array.
>>
The latency issue might improve with this rfe
6471212 need reserved I/O scheduler slots to improve I/O latency of critical
ops
-r
Tom Duell writes:
> Group,
>
> We are running a benchmark with 4000 users
> simulating a hospital management system
> running on Solaris 10 6/06 on USIV+ bas
Thanks, Neil, for the assistance.
Tom
Neil Perrin wrote On 12/12/06 19:59,:
>Tom Duell wrote On 12/12/06 17:11,:
>
>
>>Group,
>>
>>We are running a benchmark with 4000 users
>>simulating a hospital management system
>>running on Solaris 10 6/06 on USIV+ based
>>SunFire 6900 with 6540 storage ar
Tom Duell wrote On 12/12/06 17:11,:
Group,
We are running a benchmark with 4000 users
simulating a hospital management system
running on Solaris 10 6/06 on USIV+ based
SunFire 6900 with 6540 storage array.
Are there any tools for measuring internal
ZFS activity to help us understand what is g
Group,
We are running a benchmark with 4000 users
simulating a hospital management system
running on Solaris 10 6/06 on USIV+ based
SunFire 6900 with 6540 storage array.
Are there any tools for measuring internal
ZFS activity to help us understand what is going
on during slowdowns?
We have 192GB
20 matches
Mail list logo
