Okay. Welcome to lab number 17. Where would we be looking at the
different ways to March or the performance of our virtual machines
from the slab. We still have our CPU busier running.
I've put the resource pulls back to their original configuration.
So the production resource pool
is that the high value of 8000
the amount of host member used by the production,
resource pool and the guest member used
1.35 Gig 1.25 gig. Here
resource pool. I've got low shares 2000
and I've got much more host memory being used and more guest memory
to this is because of the
The additional constraints on the CPU for
resource is for that
VM. So the memory usage looks a little different between the two resource pools.
what we're going to do now is go into the Web client
I'm actually gonna open up
Let's put one there,
should automatically log me in.
It's taking a moment.
So have his window side by side. So we can see
the different performance characteristics of
of each of these V m.
Okay, so let's go to Vienna's and templates.
make this a little bit larger
and then we'll stretch this one. Just a touch.
so underneath the mantra tab
I can then see what this particular VM
Just like with the Vic Aiken. Select real time
and we can see that our processor is maxed out.
Do the same thing over here
except here. I'm going to look at my second VM. That way I can compare the two
go to the mantra tab,
and I'll set this for real time as well.
And both both these v EMS have pretty similar characteristics at this point. The CPU usage is still maxed out.
now we'll go look at the advanced
performance tab or button
and this view we can see
another chart for CPU.
Let's make this full screen for just a little bit.
The default is CPU, so we'll leave that set there. We can look at other things, but that's where most concerned about right now.
So what I can do is go to chart options
and I've already configured this one. But normally win the name of the VM would be checked here. So I'm gonna uncheck that
I'm going to de select all the counters.
So these are all the things you can display in a chart,
and we're only going to select two that were interested in
percentage of time the virtual machine was ready but could not get scheduled to run on the physical CPU.
So that's a no indication of
that. The fact that this virtual machines waiting for its chance
execute some instructions on the host CPU
and then also select used.
And this is a total CPU usage.
Okay, so the Times fan will say real time notice. Of course, we can pick other options,
but we'll stick with real time for now,
and that will start to load that graph.
We can see we've got our
our red line and our blue line,
the ready values or not
But see, if you used
kind of hovering around that 21,000 level.
let me just drag this tab here. That might be a little easier to see.
All right now I will configure the same chart settings for the Window seven clone
again. We'll go to the advanced button
and we'll click chart options.
You might have also noticed that I'm getting some more
alerts for my CPU usage being very high. So the center is trying to tell me that there are performance problems.
Of course, we know that we created those ourselves, so
that's to be expected. Okay, So I will do Select
De select all the counters
and then go ahead and select ready
Okay, So now what we can see is
now this is running for Ah, a few minutes. We can see that our average CP ready is just just over
Now, this is for the window seven V m, which has
which is in the production resource pool which has high
CPU shares allocated.
six mil seconds in 15 point
7 15,050 roughly four
ready and used. If we look at
we can see here that
No, this chart is not configured. I thought I had this one setup.
we can see that the,
we're about a little over a millisecond. Higher average for the ready value, because the other one was just over six. Now we're at seven milliseconds,
18,000 milliseconds vs,
because the machines are in different resource pools and have different CPU resource allocations,
we're able to directly
the difference in the in the performance
and the late and see that that is being felt by
by those applications. Users would be running on those systems.
So again, that's about a millisecond faster for the production VM and the 3000 milliseconds. Faster
All right, so now what I'd like to do is
stop these scripts from running,
so I'm gonna go ahead and click. Stop,
And if we go back to our web client,
the next update should show that
these values are going to be much different.
I can already see the CPU usage dropping off
And as another way of looking at the overall effect this has had, we can go back to our vic
and select our host.
Since I can do Performance monitor and the host,
you can see that the CPU was
was quite busy all over the place
during the time of this testing.
So we got very close to, ah, 100%
for all of the various cores that we're trying to
satisfy the requirements of the CPU busier tool.
And now that that's no longer running
RCP, you said should should go back down to something much lower because the
system is more or less idle.
that concludes lab number 17
We will be working with alarms.
And of course, you've already seen some of those alarms get triggered
or alerts are getting triggered
to show me that I've got
You know, my health status monitoring is, ah
telling me something's
and we'll have a little bit closer. Look at that. So we'll we'll create some alarms. That monitor for conditions will create an alarm that monitors for an event. And we'll talk about the difference between those things.
And then we can see what the what the alarms look like when they get triggered and how to acknowledge them and finally disable them.
All right. Thank you. See you in the next lap.