On Tue, Feb 15, 2005 at 04:54:52PM +0100, Max Laier wrote:
I use $vmstat -z | grep Mbuf. The netstat -m output is broken, because
fixing this would impose an additional atomic operation on each alloc/free
which is a real performance killer.
Will this behaviour stay as-is ? It's not usual
On 15 Feb, Max Laier wrote:
On Tuesday 15 February 2005 12:38, Borja Marcos wrote:
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly,
much less comprehensive. Is there any other place
On Tue, 15 Feb 2005, Borja Marcos wrote:
Looking at the mbuf statistics available in FreeBSD 4 and
FreeBSD 5 I can see that the statistics available in FreeBSD 5 are,
surprisingly, much less comprehensive. Is there any other place where I
can find out how many mbuf requests have been
On Tue, 15 Feb 2005 16:54:52 +0100, Max Laier [EMAIL PROTECTED] wrote:
On Tuesday 15 February 2005 12:38, Borja Marcos wrote:
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly
This statistic appears to have been lost during the conversion to UMA
allocating mbufs. I probably won't get to it this week, but I'll try
to
get that statistic back in the mix in the next week or two.
Unfortunately,
I will disable the MBUF statistics for now. I plan to release the
first
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly,
much less comprehensive. Is there any other place where I can find out
how many mbuf requests have been done, how many of them have waited
On Tuesday 15 February 2005 12:38, Borja Marcos wrote:
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly,
much less comprehensive. Is there any other place where I can find out
how
I use $vmstat -z | grep Mbuf. The netstat -m output is broken,
because
fixing this would impose an additional atomic operation on each
alloc/free
which is a real performance killer.
Humm. Will check the vm.zone sysctl, thanks :-)
I guess there's a lot of interesting info there, but some of
needs to be changed to accomodate this structure, but in addition to
that a way to make statistics gathering cheaper would be nice, because
currently doing a 'vmstat -z' is really terrible for performance.
Which reminds me... those of you doing benchmarks, please don't run
'vmstat -z' while you're
9 matches
Mail list logo
