Hi
in veeam one 6.5 there seems to be a discrepancy between what it says the CPU Ready has been over a month to what what Vcentre has seen over a month?
has anyone encountered this at all?
Vsphere is giving an average of CPU Ready 17247.184Milliseconds over a month and Veeam one is giving 0.23%
-
- Enthusiast
- Posts: 60
- Liked: 5 times
- Joined: Nov 28, 2012 10:23 am
- Full Name: Nick Holman
- Contact:
-
- VP, Product Management
- Posts: 27376
- Liked: 2799 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: CPU Ready discrepency
Hi Nick,
Can you please clarify how you convert "%" to "milliseconds" for the selected period of time?
Thanks!
Can you please clarify how you convert "%" to "milliseconds" for the selected period of time?
Thanks!
-
- Enthusiast
- Posts: 60
- Liked: 5 times
- Joined: Nov 28, 2012 10:23 am
- Full Name: Nick Holman
- Contact:
Re: CPU Ready discrepency
i'm basing the graph update on 2 hour refreshes on vsphere so im dividing the average 17247 by 7200 (7200000 milliseconds) and getting 2.3%?
Not 100% sure if its right but the history graphs dont give me the refresh times to base my sums on
Not 100% sure if its right but the history graphs dont give me the refresh times to base my sums on
-
- VP, Product Management
- Posts: 27376
- Liked: 2799 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: CPU Ready discrepency
Actually, the calculation should be the following - 17 247 / 7 200 000 * 100 = 0.23 %
-
- Enthusiast
- Posts: 60
- Liked: 5 times
- Joined: Nov 28, 2012 10:23 am
- Full Name: Nick Holman
- Contact:
Re: CPU Ready discrepency
I see...thats why you are who you are!
thanks!!
thanks!!
Who is online
Users browsing this forum: No registered users and 7 guests