On Sun, Feb 09, 2003 at 09:48:18PM +0100, Mattias Pantzare wrote:
> >Apply this patch in src/sys/geom and make a new kernel.
> > http://phk.freebsd.dk/patch/geom_io.patch
> >
>
> I get a Not Found from that URL.
There are many patches listed here:
http://phk.freebsd.dk/patch/
Maybe the corr
In message <[EMAIL PROTECTED]>, Mattias Pantzare writes:
>[EMAIL PROTECTED] wrote:
>> I have played with the statistics collection in GEOM a bit, and need
>> more feedback, but first: try to play with it a bit.
>>
>> Assuming you're running -current as of today, otherwise install
>> include files
[EMAIL PROTECTED] wrote:
I have played with the statistics collection in GEOM a bit, and need
more feedback, but first: try to play with it a bit.
Assuming you're running -current as of today, otherwise install
include files and libgeom by hand first.
Apply this patch in src/sys/geom and make a
I have played with the statistics collection in GEOM a bit, and need
more feedback, but first: try to play with it a bit.
Assuming you're running -current as of today, otherwise install
include files and libgeom by hand first.
Apply this patch in src/sys/geom and make a new kernel.
http
At 9:54 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
My understanding was that a disk is 100% busy, if the heads are
constantly moving to and fro, and there is no period of time when
they aren't being yanked around. In other words, it would be 100% if
there is always at least one outstanding r
In message , Brad Knowles writes:
>At 8:26 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
> My understanding was that a disk is 100% busy, if the heads are
>constantly moving to and fro, and there is no period of time when
>they aren't being yanked around.
At 8:26 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
Is a disk 100% busy if it has requests outstanding at all times,
but could handle five times as many requests because they could be
sorted into the current stream of requests free of cost ? Or is
it only 20% busy ? How do you measure it
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
writes:
>2. %busy. I personally think this is the most important one, but as
>you say, there's no reason not to do the others as well.
The problem with this one is that we can't measure it in a way which
tells us the truth, and we may n
On Wednesday, 5 February 2003 at 1:07:47 +0100, Poul-Henning Kamp wrote:
> In message , Brad Knowles writes:
>> At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
>>
>>> In difference from the devstat framework which measures how big a
>>> percentage o
On Tue, 4 Feb 2003, Poul-Henning Kamp wrote:
>
>
>
> Now, discussion time:
>
> The timestamps cost something to make, and my plan was to only collect
> them while a monitoring program is running. (Is this a good idea ?)
>
probably it is a good idea though it does lead to the possibility of
At 1:07 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
I don't have a queue-depth as such, but I have number of transactions
in transit. Will a snapshot of that at the time of the read do
what you want ? I am too sleepy to know if that will allow you to
calculate the average number of outsta
In message , Brad Knowles writes:
>At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
>
>> In difference from the devstat framework which measures how big a
>> percentage of the time a drive has one or more outstanding requests,
>> I think that measurin
At 4:58 PM -0600 2003/02/04, Dan Nelson wrote:
I pressume we also want to collect number of bytes transferred, and
I will add that in the next iteration.
Definitely. What I'd like is enough statistics to be able to duplicate
Solaris' iostat -x output:
You know, that is *precisely* what
At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
In difference from the devstat framework which measures how big a
percentage of the time a drive has one or more outstanding requests,
I think that measuring the responstime is a much more useful metric.
(comments, input, references welco
In the last episode (Feb 04), Poul-Henning Kamp said:
> Collecting number of operations and number of errors is a nobrainer.
>
> The timestamps cost something to make, and my plan was to only
> collect them while a monitoring program is running. (Is this a good
> idea ?)
>
> In difference from t
I have created a patch which contains a preview of the statistics
code I intend to add to GEOM, and would invite people to play with
it and give me some feedback:
http://phk.freebsd.dk/patch/geom_iostat.patch
Here is a small shell-script to watch the output with:
http://phk.free
16 matches
Mail list logo