- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- evaperf sample durations
Disk Enclosures
1753808
Members
8014
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2009 02:32 AM
12-16-2009 02:32 AM
evaperf sample durations
Hi,
I'm setting up evaperf scripts to collect 5-minute averages with -cont 300 from our 8100's. At the moment I do this for each 24 hour period, but if it falls over for any reason I lose a whole days data. So I'm now rewriting it to collect for an hour, every hour and amalgomating.
However one thing I've noticed worries me a little. If we run a command something like: -
evaperf" mof -cont 300 -dur 86100 -csv -od c:\evaperf_data
The first sample (e.g. midnight) is returned immediately.
Am I correct in thinking that this first sample is a "point in time" sample, and not representative of the previous 5 minutes? My testing seems to suggest that this is the case.
The reason this is worrying is that we amalgomate the MB/s figures for each of our vdisks and multiply by the number of seconds in the sample to get an estimate of total throughput for CA journal log sizing purposes. If this first sample isn't representative of the average through the full 5 minutes and only represents e.g. 1 second, then this will throw the figures out. Not so bad when it's once a day, but if we run it once an hour it could be that 5 out of every 60 minutes of data is bogus so overall figures out by up to 10%.
Has anyone accounted for this before?
I'm setting up evaperf scripts to collect 5-minute averages with -cont 300 from our 8100's. At the moment I do this for each 24 hour period, but if it falls over for any reason I lose a whole days data. So I'm now rewriting it to collect for an hour, every hour and amalgomating.
However one thing I've noticed worries me a little. If we run a command something like: -
evaperf" mof -cont 300 -dur 86100 -csv -od c:\evaperf_data
The first sample (e.g. midnight) is returned immediately.
Am I correct in thinking that this first sample is a "point in time" sample, and not representative of the previous 5 minutes? My testing seems to suggest that this is the case.
The reason this is worrying is that we amalgomate the MB/s figures for each of our vdisks and multiply by the number of seconds in the sample to get an estimate of total throughput for CA journal log sizing purposes. If this first sample isn't representative of the average through the full 5 minutes and only represents e.g. 1 second, then this will throw the figures out. Not so bad when it's once a day, but if we run it once an hour it could be that 5 out of every 60 minutes of data is bogus so overall figures out by up to 10%.
Has anyone accounted for this before?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2009 05:25 AM
12-16-2009 05:25 AM
Re: evaperf sample durations
Right, I've done some more investigation and it is indeed correct that the first sample is inaccurate as it only represents a point-in-time rather than an average. You can see this from the attached graph.
I basically scheduled a 60 second continuous collection, then another 5 minutes later, and another, and another, ending up with 4 separate collects running. You can see that the first point of each subsequent collection is off-the-line, and from then on they match perfectly.
So it seems that to get truly accurate data from evaperf, you need to ignore the first time point of any collection. For me that means collecting every 60 minutes for 65 minutes and binning the overlapping time in each subsequent file via a script.
Hopefully this will help if anyone searches for similar issues in future.
I basically scheduled a 60 second continuous collection, then another 5 minutes later, and another, and another, ending up with 4 separate collects running. You can see that the first point of each subsequent collection is off-the-line, and from then on they match perfectly.
So it seems that to get truly accurate data from evaperf, you need to ignore the first time point of any collection. For me that means collecting every 60 minutes for 65 minutes and binning the overlapping time in each subsequent file via a script.
Hopefully this will help if anyone searches for similar issues in future.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP