so you've got all the best hardware CPU
GPU ssds the good stuff but for some
reason your rig is still slow despite
having the best of the best you're experiencing noticeable stuttering and
serious downtime well I'm no doctor but
it's possible that your system is getting spammed by interrupt requests
interrupt requests typically aren't a bad thing in fact they're essential to
the basic momentto moment functioning of your computer sometimes in order order
to take an action your system needs to ask the processor to interrupt code that
is currently being executed if the processor accepts the request it pauses
its activity saves its state and executes an interrupt Handler otherwise
known as an interrupt service routine or ISR after the new task is finished the
processor resumes the interrupted process but not just any task gets to
burst in like the Kool-Aid man and demand to take Center Stage your
computer runs BAS based on a strict hierarchy of priority essential urgent
tasks come first and can interrupt any other task nonessential non-urgent tasks
will either share available resources or wait in line for their turn handing over
control when necessary to more important processes then there's tasks in the
middle urgent enough to interrupt low priority tasks but not so urgent that
they get actioned immediately over anything else we all know the feeling
however however some critically important interrupt requests will come
with a timeout counter that resets the system if it's unable to run its
essential task before the time runs out while the system can decide when and if
it will accept an interrupt request once that interrupt is accepted and its
action is in progress the CPU or GPU
servicing the request cannot be interacted with by the rest of the
system most interrupts happen quickly and seamlessly but longer than usual
interrupts or large large numbers of interrupt requests can cause stuttering
or result in dropped packets and higher latency when networking longer than
usual interrupts are often the result of misbehaving Hardware but some devices
like Wi-Fi adapters flood the system with interrupt requests which increases
the likelihood that part of the system will stall there are also times when
bugs and glitches have caused the usually clear hierarchy of priority to
get jumbled leading to perhaps the most severe consequence of interrupt requests
a little thing called priority inversion or thrashing we'll explain what that is
and how to avoid it after we say thanks to our sponsor Corsair Corsair custom
lab allows you to create a gaming setup as unique as you are start with a
product like their K65 plus wireless keyboard and select from a variety of
different themed key caps to match your style from there you can add a mouse and
a mouse pad to complete the look Corsair handles all the heavy lifting for you
just make your Custom Creation and they'll build it and ship it right to
you learn more at the link in the description priority inversion is a
situation where the strict task priority hierarchy that allows a computer to make
decisions is violated this can happen when a high priority and low priority
task both need to use a resource that can only do one task at a time if the
low priority task is running and it gets interrupted by a medium priority task
that doesn't need the specific exclusive resource that it's using that might
trigger a bug that causes the low priority task to refuse to relinquish
its hold if the system then attempts to run a high priority task that requires
that exclusive resource it will be inadvertently blocked by the interrupt
instigated by the medium priority task this can then cause the system to stall
and time out and it's exactly what happened to the sojer Rover on Mars in
1997 the Rover's low priority weather data collection task required an
exclusive lock on the Rover's information bus this task was then
interrupted and paused by a long duration medium priority communication
task which held that exclusive lock on the information bus in place this then
inadvertently blocked a high priority task from servicing the information bus
the Rover system would then time out and initiate a full system reset this
happened four times and was only resolved by the most remote of remote
debugging NASA used a double of sojer
back on Earth to test a solution and then sent the patch to the robot on Mars
resolving the issue while your computer is in many ways more sophisticated than
a computer from 1997 even a cool robot
space computer it's still vulnerable to the Slowdown that comes with your
computer spending its valuable processing power deciding what to do
rather than just doing it not to mention the errors that can happen when your
machine is trying to juggle several tasks at once so if you have ad8 D like
me and somebody just criticizes you for your indecisiveness and procrastination
just tell them you're experiencing an unfortunate priority inversion and
consequent thrashing it worked for me you know what else worked for me you
watching this whole video thanks so much like the video if you liked it dislike
it if you disliked it check out our other videos comment below with video
suggestions and don't forget to subscribe and follow after you get
through the the Quee of things that you have to think about before and then do
it