Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*disk\.dev\.avactive\s+and\s+disk\.dev\.aveq\s+on\s+RH\s+Advanced\s+Server\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*disk\.dev\.avactive\s+and\s+disk\.dev\.aveq\s+on\s+RH\s+Advanced\s+Server\s*$/: 12 ]

Total 12 documents matching your query.

1. Re: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Sun, 13 Apr 2003 09:11:05 +1000 (EST); Apart from the scaling problem in the Linux PMDA that Todd reported later with disk.dev.avactive and disk.dev.aveq, I am unaware of any problems with these metrics. Since the time metrics are in unit; /archives/pcp/2003-04/msg00001.html (12,187 bytes)
2. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Sun, 13 Apr 2003 09:11:18 +1000 (EST); Well spotted. The reason we had not found this earlier is that most of our Linux testing has been done on machines where HZ is 1024, so * 1000 / 1024 introduces only a very small error. Of course if; /archives/pcp/2003-04/msg00002.html (9,604 bytes)
3. Re: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Sun, 13 Apr 2003 09:11:05 +1000 (EST); Apart from the scaling problem in the Linux PMDA that Todd reported later with disk.dev.avactive and disk.dev.aveq, I am unaware of any problems with these metrics. Since the time metrics are in unit; /archives/pcp/2003-04/msg00008.html (12,278 bytes)
4. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Sun, 13 Apr 2003 09:11:18 +1000 (EST); Well spotted. The reason we had not found this earlier is that most of our Linux testing has been done on machines where HZ is 1024, so * 1000 / 1024 introduces only a very small error. Of course if; /archives/pcp/2003-04/msg00009.html (9,680 bytes)
5. disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: "Davis, Todd C" <todd.c.davis@xxxxxxxxx>; Date: Tue, 18 Mar 2003 08:36:01 -0800; With no disk activity on the system I see disk.dev.avactive and disk.dev.aveq on the root drive. The last sample had some disk io but the disk.dev.avactive number did not change and disk.dev.aveq num; /archives/pcp/2003-03/msg00022.html (9,647 bytes)
6. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: "Davis, Todd C" <todd.c.davis@xxxxxxxxx>; Date: Wed, 19 Mar 2003 11:42:58 -0800; I think I found part of the bug for these metrics. The metrics are being converted to milliseconds twice, in the sard patch and in the Linux pmda: From sard patch: +#define MSEC(x) ((x) * 1000 / HZ); /archives/pcp/2003-03/msg00024.html (11,342 bytes)
7. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Fri, 21 Mar 2003 06:01:55 +1100 (EST); I should read _all_ my mail backlog before responding. Yep Todd, this looks busted. But I believe the Linux PMDA conversion dates from some version of the sard patch (or similar) in the past that did; /archives/pcp/2003-03/msg00025.html (14,436 bytes)
8. Re: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Fri, 21 Mar 2003 04:52:18 +1100 (EST); The counters are correct. The semantics of these metrics are brain-dead from birth ... a genetic weakness passed down through the generations from sadc in Unix edition 7 or thereabouts. When we get t; /archives/pcp/2003-03/msg00026.html (8,515 bytes)
9. disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: "Davis, Todd C" <todd.c.davis@xxxxxxxxx>; Date: Tue, 18 Mar 2003 08:36:01 -0800; With no disk activity on the system I see disk.dev.avactive and disk.dev.aveq on the root drive. The last sample had some disk io but the disk.dev.avactive number did not change and disk.dev.aveq num; /archives/pcp/2003-03/msg00049.html (9,662 bytes)
10. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: "Davis, Todd C" <todd.c.davis@xxxxxxxxx>; Date: Wed, 19 Mar 2003 11:42:58 -0800; I think I found part of the bug for these metrics. The metrics are being converted to milliseconds twice, in the sard patch and in the Linux pmda: From sard patch: +#define MSEC(x) ((x) * 1000 / HZ); /archives/pcp/2003-03/msg00051.html (11,357 bytes)
11. RE: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Fri, 21 Mar 2003 06:01:55 +1100 (EST); I should read _all_ my mail backlog before responding. Yep Todd, this looks busted. But I believe the Linux PMDA conversion dates from some version of the sard patch (or similar) in the past that did; /archives/pcp/2003-03/msg00052.html (14,499 bytes)
12. Re: disk.dev.avactive and disk.dev.aveq on RH Advanced Server (score: 1): Author: kenmcd@xxxxxxxxxxxxxxxxx; Date: Fri, 21 Mar 2003 04:52:18 +1100 (EST); The counters are correct. The semantics of these metrics are brain-dead from birth ... a genetic weakness passed down through the generations from sadc in Unix edition 7 or thereabouts. When we get t; /archives/pcp/2003-03/msg00053.html (8,563 bytes)

Current List: 1 - 12
Page: [1]