[Autogenerated] what about that?
Quantum?
The time slice every threat gets when it executes and that would be
the maximum time it can run before another threat that has the same
priority also wants to run and so we know that we have a timer that
takes in a specific intervals and the different interval is 15.625
milliseconds.
That's the time of the schedule works with.
In fact there's a tool from 16 tunnels that can easily show us this
number and I'll show you that in the next demo now.
The way the Quantum is built today is that the
default Quantum on client systems.
Client systems are home edition pro enterprise and so on is two clock ticks.
So it's roughly 31 point something milliseconds.
And so I said 30 milliseconds in one of the previous
videos but that was a rough number really.
The default several Quantum is 12 of these clock ticks,
which means it's roughly 186 something milliseconds.
You might be wondering why do we have a longer Quantum service systems.
And the basic idea is that the several machine is typically a machine that is
stored on some server room might not be used interactive by anyone and mostly
host services that listen to client requests.
And once the client request comes in having a longer Quantum
provides better opportunity or larger,
I would say um ability to serve the client in a single Quantum,
that's more efficient than having to suffer several context,
which is because the operation is takes might take longer than the client.
Quantum,
So that's kind of the rationale behind selecting a longer Quantum
for server systems as we see in the next demo,
it's something we can change now.
Normally these are the Quantum's that we get and we can
change them by using the registry.
There's some tweaks we can do, which I won't show you here,
but you can find more details in the Windows internals
book if you care or a job object.
The job object when running on service systems allows some flexibility in
the Quantum for processes that are part of that job.
Another feature that occurs only on client machines is
something called quantum boosting.
The idea of quantum boosting is that for the foreground process and the
foreground process is defined as the process that one of its threats is
currently is the one that's created the window that is currently being used
by the users so it's currently active.
And this process meaning all the threats in that process get by default,
triple Quantum instead of 30 milliseconds,
rafi, they get 90 milliseconds.
And again,
the rationale here is that because this is a
process of the user cares about more,
then perhaps it's a good idea to let threats there run longer.
If there are other threats with the same priority also waiting to run.
So if I have something like Word and Excel running at the same time and I'm
currently running looking at world working with Word and Excel is calculating
the state of all protons in the universe or something,
but it's not the part of the active window right now,
then I expect world to behave nicer to me as a user.
So if you do something with world, I expected,
I expect to get better responsiveness.
And this happens because of quantum boosting and also
because UI threats get plus two bonus as as priority
booth when they receive a message,
which again makes sense on the client machine where there's
typically interactive user working with the machine.