Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
00:00:08,400 --> 00:00:12,720
Hey, I'm Dave, welcome to my shop! I'm
Dave Plummer, a retired operating systems
00:00:12,720 --> 00:00:16,240
engineer from Microsoft going back
to the MS-DOS and Windows 95 days.
00:00:16,880 --> 00:00:22,160
I worked on pretty much every operating system
at Microsoft from MS-DOS through Sever 2003,
00:00:22,160 --> 00:00:27,600
and today I'm going to explain not only why it is
that your computer slows down as it ages, but also
00:00:27,600 --> 00:00:33,120
the Top 5 things that you can do to fix it right
now.
I figure there are two scenarios that bring
00:00:33,120 --> 00:00:37,120
you to this point. Either you're contending
with some ancient piece of iron yourself,
00:00:37,120 --> 00:00:42,560
or to deploy into some secondary capacity in
your home lab. The other, perhaps more likely
00:00:42,560 --> 00:00:46,880
possibility is that you've taken mercy upon one
of your relatives who is using an older computer
00:00:46,880 --> 00:00:50,960
where the performance can best be measured on
a geological timescale. But is there actually
00:00:50,960 --> 00:00:54,880
anything you can do about it? The answer is yes,
there are actually several things that can and
00:00:54,880 --> 00:00:59,760
should be done, and we'll cover them all today!
You might think its unavoidable, but it's actually
00:00:59,760 --> 00:01:05,120
a ciumulative process that happens over time, and
it's at least mostly reversible. That means you
00:01:05,120 --> 00:01:09,040
can usually correct a lot of the slowdown problems
with the Top 5 Tips I'll share with you today.
00:01:09,680 --> 00:01:13,360
Now you might think that I would only have
the latest and greatest hardware for myself,
00:01:13,360 --> 00:01:16,880
and that vendors and manufacturers constantly
shower me with the best of the best.
00:01:17,440 --> 00:01:22,160
And if my main desktop is in fact a Mac Ultra
Studio connected to a Threadripper rocking 128
00:01:22,160 --> 00:01:27,120
gigs of RAM, you might find it hard to muster
any sympathy for me whatsoever. And that's fine.
00:01:27,120 --> 00:01:31,280
But don't worry about me. Think of the children.
Specifically, think of MY children!
00:01:31,280 --> 00:01:35,920
That's because our house is equipped with what is
known as The Craft Room. It's almost like a tiny
00:01:35,920 --> 00:01:39,840
classroom in that each kid has a little locker
and then a desk area reserved at the big counter.
00:01:40,560 --> 00:01:44,480
The whole area is overlooked by mom's desk,
and perhaps one of the best decisions we ever
00:01:44,480 --> 00:01:48,400
made was to make this room the central point
of most all family activity in the house.
00:01:49,120 --> 00:01:52,880
We did this by putting each kid's computer
down here instead of in their room.
00:01:53,440 --> 00:01:56,800
This also allowed us the ability to at least
keep an eye on what the kids are spending most
00:01:56,800 --> 00:02:01,360
of their time on, though of course they all have
iPads and phone as well, so it's not exclusive.
00:02:01,360 --> 00:02:05,440
When I initially built out this space with
computers for the kids, I knew I didn't want
00:02:05,440 --> 00:02:10,320
a bunch of PC boxes sitting up on top. I
really wanted the elegance, uniformity,
00:02:10,320 --> 00:02:15,440
and simplicity of the iMac hardware, but I was
a loyal Microsoft employee, so.... As a result,
00:02:15,440 --> 00:02:19,120
I wound up buying iMacs, wiping them, and
then using Bootcamp to install the latest
00:02:19,120 --> 00:02:24,000
and greatest version of Windows onto the Apple
hardware. To me, it was the best of both worlds!
00:02:24,560 --> 00:02:28,720
But there is one fatal flaw with the iMac, being
that when the computer ages, you've still got a
00:02:28,720 --> 00:02:33,200
big investment in the display, which is still
perfectly fine, after all. No one is going to
00:02:33,200 --> 00:02:38,880
throw away a perfectly fine 27" 4K or 5K monitor,
but other than RAM you're very much locked into
00:02:38,880 --> 00:02:44,640
the iPad's CPU and other hardware. As a result, I
think a lot of people, myself included, persist in
00:02:44,640 --> 00:02:49,200
using iMacs with base hardware specs that we'd
otherwise haul off to PC Recycle if not for the
00:02:49,200 --> 00:02:54,240
expensive display. And so, I've become a bit of an
expert at extending the life of older machines.
00:02:54,800 --> 00:02:58,960
Before we can fix any of it, though, we first need
to understand why the computer slows down with
00:02:58,960 --> 00:03:04,400
age.
Now clearly, the hardware's not actually
getting any slower, as components to not slow down
00:03:04,400 --> 00:03:08,640
with age, and unlike the unbridled raw speed you
experience while that new-computer smell is still
00:03:08,640 --> 00:03:12,480
fresh, the slowdown that's been happening
since is probably not just in your head.
00:03:13,280 --> 00:03:16,320
Just to get it out of the way, because
it's
Something that CAN happen, however,
00:03:16,320 --> 00:03:21,200
which would be clogged vents, fans, or heat syncs
that wind up causing premature thermal throttling.
00:03:21,200 --> 00:03:27,680
That's about the only real way I can imagine
hardware performance varying with age. Software,
00:03:27,680 --> 00:03:32,960
though, is a completely different story. But why?
The major reason is that software installations,
00:03:32,960 --> 00:03:37,146
and in particular the alternating or rotating
installation and removal of games and software, is
00:03:37,146 --> 00:03:40,240
that they cause the amount of code that the system
has to execute to grow and bloat and that strains
00:03:40,240 --> 00:03:44,800
the resources of the machine in a way it did not
when it was new. And the real problem is that
00:03:44,800 --> 00:03:49,680
sometimes, if you double the load on PC it might
become 4 times slower, as it's not always linear.
00:03:49,680 --> 00:03:54,960
For example, if you need 16G on a machine that
has only 8G, it must instead use extremely slow,
00:03:54,960 --> 00:03:59,520
disc-based virtual memory instead, and that is
orders of magnitude slower than direct memory
00:03:59,520 --> 00:04:04,640
access. And conversely that is why sometimes
a small change can have a big impact on perf.
00:04:05,760 --> 00:04:12,160
#1 - Removing Unused Applications and Games
It
seems simple, because it is: go into the control
00:04:12,160 --> 00:04:16,720
panel and remove any applications that you're not
using. You should also be judicious about what
00:04:16,720 --> 00:04:21,120
you install on your machine if it's not something
you want to become part of your permanent toolset;
00:04:21,120 --> 00:04:26,240
consider evaluating games and utilities in a VM
if possible. Not all game systems are created
00:04:26,240 --> 00:04:30,160
equally - perhaps it's entirely fine to check out
and remove and reinstall dozens of games with a
00:04:30,160 --> 00:04:34,960
system like Steam but its less so if those games
are also partying all over the system registry.
00:04:35,680 --> 00:04:39,360
Speaking of which, the registry is one
reason why it's important to use the
00:04:39,360 --> 00:04:43,920
uninstaller for an application. If written
correctly, and that's anything but a given,
00:04:43,920 --> 00:04:48,000
the uninstaller will remove not only the files
and folders that it created during the original
00:04:48,000 --> 00:04:51,760
installation but also things like fonts and
entries in the system registry database.
00:04:52,480 --> 00:04:57,520
Uninstalling a large and complex application
can clean out a large swath of registry debris.
00:04:58,320 --> 00:05:02,400
There are programs that claim to be able to do
registry repair and cleaning after the fact but
00:05:02,400 --> 00:05:07,280
doing it well and safely is not trivial. Better
to use the application's proper uninstaller.
00:05:09,120 --> 00:05:12,800
One thing you may not have considered is that
if you have a computer that's 8 years old,
00:05:12,800 --> 00:05:16,720
you're likely not still running all 8-year-old
software on it. Odds are you've upgraded your
00:05:16,720 --> 00:05:20,800
software along the way and that those newer
versions have grown in size and resource demands.
00:05:21,360 --> 00:05:25,760
So, in that sense, your computer hasn't really
gotten any slower, you're just asking something
00:05:25,760 --> 00:05:30,800
different of it, and the performance that results
is terrible.
There are other perceptual changes
00:05:30,800 --> 00:05:34,960
that also might come about, such as perhaps you
get the new iPhone that responds quite promptly.
00:05:34,960 --> 00:05:39,440
If you then go to use a desktop application and
it responds more slowly than your phone does,
00:05:39,440 --> 00:05:43,680
it will feel even slower by comparison, even if
nothing has actually changed on the computer.
00:05:44,240 --> 00:05:48,880
But let's say you've ruled out simple perceptual
changes, and that your computer really is getting
00:05:48,880 --> 00:05:56,960
slower. What can you do about it?
Well, the first
thing might seem so minor that you overlook it,
00:05:56,960 --> 00:06:00,480
but it's actually very important: you always
keep your computer up to date with the latest
00:06:00,480 --> 00:06:05,120
operating system and application patches and
updates. Certainly, operating systems can and
00:06:05,120 --> 00:06:09,200
do grow significantly from one major version
to next, but my experience was been that they'd
00:06:09,200 --> 00:06:15,120
actually get faster within minor versions along
the way. For example, Win95 OSR2 was faster than
00:06:15,120 --> 00:06:20,960
the original Windows 95. At the same tasks, XP
was faster than NT4 which was faster than 3.51
00:06:20,960 --> 00:06:26,640
which was faster than 3.5 which had already been a
big improvement over 3.1. How can that be?
Well,
00:06:26,640 --> 00:06:30,400
I can't prove it, but what I saw from inside the
industry was that we'd add features on the major
00:06:30,400 --> 00:06:34,720
version increments and then fix bugs and improve
performance for the minor version increments.
00:06:34,720 --> 00:06:40,560
And it just makes sense - new operating systems
are sold on new features. As a result, first
00:06:40,560 --> 00:06:44,400
you get the features, then we make them fast.
But you can't always do both from the outset.
00:06:45,120 --> 00:06:49,520
This is also true of drivers, particularly
graphics drivers. They are constantly evolving
00:06:49,520 --> 00:06:54,080
and being tweaked. And since many drivers
are unified across a wide array of hardware,
00:06:54,080 --> 00:06:58,480
perhaps your 1070GTX will pick up a feature
or some perf in the release of the new Nvidia
00:06:58,480 --> 00:07:03,200
drivers even years later. The same can be
true for new releases of things like DirectX.
00:07:03,840 --> 00:07:08,800
And because the release dates of operating
systems, drivers, SDKs, and updates are staggered,
00:07:08,800 --> 00:07:12,560
the best thing you can do is to just keep
everything up to date with the latest versions of
00:07:14,480 --> 00:07:21,360
stable platforms.
After that, however, we can
start to get more proactive and actually undo
00:07:21,360 --> 00:07:25,280
some of the performance degradation. One of
the first things we need to check is to see
00:07:25,280 --> 00:07:28,960
what programs are starting automatically
with Windows. Everything that runs during
00:07:28,960 --> 00:07:33,280
startup will by definition slow your startup
down, and those things that continue running
00:07:33,280 --> 00:07:36,320
after startup will become a permanent
part of the base load of the machine.
00:07:37,280 --> 00:07:42,320
One of the most important statistics about Windows
is the total working set. That is the sum total of
00:07:42,320 --> 00:07:46,800
all the memory that the operating sytems and
application have asked for at any one time.
00:07:47,520 --> 00:07:51,600
Of course that total may exceed the amount of
physical memory you have, and as noted earlier,
00:07:51,600 --> 00:07:55,600
once pushed to start using virtual memory to
make up for the shortfall, performance craters.
00:07:56,320 --> 00:08:01,200
Adding RAM to your system, if possible, would
be one solution.
For an even easier solution,
00:08:01,200 --> 00:08:05,680
just say hello to my little friend, Task Manager.
I wrote the original Task Manager because I was
00:08:05,680 --> 00:08:09,520
curious about these kinds of statistics on my
own machine and how to tweak and optimize it.
00:08:10,080 --> 00:08:14,480
And one of the key features of Task Manager is
its ability to manage the list of programs that
00:08:14,480 --> 00:08:19,040
are started automatically with Windows when
the desktop starts. Switch to the Startup tab
00:08:19,040 --> 00:08:24,240
of Task Manager to access and modify the list.
One nice feature here is that you can disable an
00:08:24,240 --> 00:08:29,360
entry without removing it entirely. That allows
you test that every still works properly when
00:08:29,360 --> 00:08:34,560
you've turned off a startup application. But what
can you turn off? Generally, I'd suggest turning
00:08:34,560 --> 00:08:38,160
off only those things that you're certain you
know what they do and that you do not need them.
00:08:38,720 --> 00:08:43,040
Perhaps there are larger programs like Skype
that are starting in the background each time.
00:08:43,040 --> 00:08:47,760
If you never need to receive calls, or don't
use Skype at all, go ahead and turn it off.
00:08:48,400 --> 00:08:53,120
If you're unsure, I suggest that you don't turn
it off. If you must, turn off one thing at a time,
00:08:53,120 --> 00:08:58,560
reboot and test for any problems. Don't delete
the entries entirely, just disable their checkbox.
00:08:58,560 --> 00:09:02,880
By the way, if you're on some seriously older
software like Windows 7, this feature wasn't
00:09:02,880 --> 00:09:07,360
in Task Manager yet so you'll need to use a
program supplied with Windows called msconfig
00:09:07,360 --> 00:09:13,920
to do much the same thing.
Next, we have hard
disk problems. A number of the things I'll talk
00:09:13,920 --> 00:09:19,040
about in this section only apply to magnetic media
and not SSDs, but some things, like bloated and
00:09:19,040 --> 00:09:24,400
abandoned temporary files, seemingly never change.
Let's go through the list.
Mechanical drives
00:09:24,400 --> 00:09:28,800
suffer from file fragmentation over time, which
means one file is forced to be scattered around
00:09:28,800 --> 00:09:33,280
the hard drive, so the heads have to jump and move
around even to read a single linear file, because
00:09:33,280 --> 00:09:37,920
there just wasn't enough room to store that file
linearly on disk. In the old days you'd fix this
00:09:37,920 --> 00:09:42,720
with a defrag, though it's much less important
with NTFS than it was with the FAT filesystems.
00:09:43,520 --> 00:09:47,840
I've heard some folks, including other well-known
YouTube creators, make the claim that as computers
00:09:47,840 --> 00:09:51,360
age they're forced to grow the hard drive
storage into areas where the actual media on
00:09:51,360 --> 00:09:56,720
the platter has a lower angular velocity in terms
of rotational speed. They argue that the speed of
00:09:56,720 --> 00:10:01,520
the media under the drive head is going to be much
faster at the outer edges than the inner tracks,
00:10:01,520 --> 00:10:06,480
and that this results in slower disk transfers.
It's an interesting theory, but ignores the fact
00:10:06,480 --> 00:10:10,880
that almost all magnetic computer media uses
what's known as constant angular velocity.
00:10:10,880 --> 00:10:16,080
Regardless of where the heads are, the platter is
always rotating at the same speed. The heads still
00:10:16,080 --> 00:10:20,400
read and write bits at the same timing as before,
and so the bits don't actually come in any faster:
00:10:20,400 --> 00:10:25,600
instead, they are spread further apart. That's why
hard disk geometry is quoted in bytes per sector,
00:10:25,600 --> 00:10:30,080
sectors per track, and heads per track. The
sectors per track number stays constant in most
00:10:30,080 --> 00:10:35,200
conventional media. Modern drives effectively use
a monolithic block count and index and abstract
00:10:35,200 --> 00:10:40,240
the real geometry away from you, but I could not
locate any drives with variable geometry offhand.
00:10:40,240 --> 00:10:44,320
If you know of any, please let me know in the
comments!
It's also pretty common for disk
00:10:44,320 --> 00:10:47,840
formats to store the directory and file allocation
information in the middle of the disk. If the
00:10:47,840 --> 00:10:51,120
outside edge of the media were significantly
faster, it's a safe bet that that's where the
00:10:51,120 --> 00:10:54,480
filesystem authors would have stored their most
important info, but it's just not the case.
00:10:55,520 --> 00:10:59,600
Now, it's worth noting that sectors per track was
actually variable in some floppy disc formats,
00:10:59,600 --> 00:11:03,680
like the Apple II and Commodore, where they
pack additional sectors into the outer tracks.
00:11:13,120 --> 00:11:16,960
Next we have the simple tasks of temporary
files and junk that can clutter up your machine,
00:11:16,960 --> 00:11:21,520
an that brings us to an essential program for
your system maintenance is named WinDirStat.
00:11:21,520 --> 00:11:25,840
It's an open-source GPL app that scans your
system to build a map of how every byte on
00:11:25,840 --> 00:11:31,200
your disk is used. Files are grouped by location
and colored by type so with a little practice
00:11:31,200 --> 00:11:35,920
you should be able to spot both single large files
and large groups of small files. Either should be
00:11:35,920 --> 00:11:40,560
investigated to determine if it's something you
can remove.
Don't delete anything you're not sure
00:11:40,560 --> 00:11:44,880
about, and don't delete anything until you're
certain you've got a working system backup.
00:11:45,440 --> 00:11:49,680
Some things, like simply emptying the recycle
bin, are pretty low risk but don't just start
00:11:49,680 --> 00:11:54,400
nuking large files that you're not familiar with!
For example, in the root folder of your boot drive
00:11:54,400 --> 00:11:59,840
there very well might a file hiberfile.sys, and it
takes up gigabytes of space, but don't delete it.
00:11:59,840 --> 00:12:04,240
Now, like me, you might say "But I've never used
hibernate in my life and don't plan to start!".
00:12:04,240 --> 00:12:09,040
If that's the case, you should use the power cfg
/hibernate option to disable the feature, which
00:12:09,040 --> 00:12:15,760
will in turn remote the file. Let's take a quick
look: mine is 27 gigabytes in size. That's huge!
00:12:15,760 --> 00:12:20,480
But if I run powercfg and turn hibernate off, it's
gone and I get the 27 gigabytes of space back.
00:12:20,480 --> 00:12:24,080
That alone could be worth the price of
admission to this video, so you're welcome!
00:12:24,080 --> 00:12:29,200
The other big one is pagefile.sys, and it's pretty
much required. However, if you have more than one
00:12:29,200 --> 00:12:32,800
drive, you can move it to a different drive, and
it's something I would recommend doing if you have
00:12:32,800 --> 00:12:37,920
a drive that's faster than your boot volume or if
you're pressed for space on that boot volume.
The
00:12:37,920 --> 00:12:42,400
only problem is that they've seriously buried the
setting! It's not available in the new settings
00:12:42,400 --> 00:12:47,920
UI and keeps getting pushed further and further
into the murky depths of the old UI. To get there,
00:12:47,920 --> 00:12:53,280
we start at System. Next we select Advances
System Settings. Oh, but were' not even close.
00:12:53,280 --> 00:12:57,520
We next go to the Advanced tab and click on
the button in the Performance Settings section.
00:12:57,520 --> 00:13:02,480
From there we click on the Advanced tab yet
again, then virtual memory, and finally,
00:13:02,480 --> 00:13:07,360
we select change.
Now as I said you need to have
a paging file but where it lives is up to you.
00:13:07,360 --> 00:13:11,600
If you wish to move yours to another drive here, I
suggest that you create a system-managed pagefile
00:13:11,600 --> 00:13:15,680
on the desired drive and then remove the
original system-managed one on the boot drive.
00:13:15,680 --> 00:13:17,920
It won't take effect until
you restart the system.
00:13:22,560 --> 00:13:26,880
Your next step, and don't assume it's not
important, is scanning for viruses and malware.
00:13:26,880 --> 00:13:31,360
It's not so much that the virus itself actually
consumes very much in terms of resources, but
00:13:31,360 --> 00:13:35,600
malicious code might very well install software
that harvests your PC resources to become a
00:13:35,600 --> 00:13:40,240
spambot or crypto-mining zombie, either
of which will definitely slow things down.
00:13:40,240 --> 00:13:44,960
Your most precious PC resources like RAM and CPU
will be used for nefarious purposes and therefore
00:13:44,960 --> 00:13:49,360
not available for your own use!
There are tons
of antivirus programs out there, but I'm going
00:13:49,360 --> 00:13:53,440
to put a stick in the ground here and say that all
you really need is Microsoft Defender. They've got
00:13:53,440 --> 00:13:57,200
their top people on it, and I know that for a fact
because the guy that runs dev for it used to work
00:13:57,200 --> 00:14:01,760
for me, and he's really good. I trust them with
my security, and you likely should as well. After
00:14:01,760 --> 00:14:05,040
all, the Defender team is not selling anything
and they're trying to bolster the security image
00:14:05,040 --> 00:14:09,520
of Windows. It's a win/win when your interests are
that closely aligned and no money changes hands!
00:14:14,480 --> 00:14:19,280
It's worth your time to check two things on
your disk: run a chkdsk to scan for errors.
00:14:19,280 --> 00:14:23,760
You CAN supply the /F option to ask it to
automatically fix anything it finds wrong,
00:14:23,760 --> 00:14:26,880
but I prefer to do a separate scan pass
first so I know what my options are.
00:14:28,400 --> 00:14:34,080
You can also run the system file scanner, sfc
/scannow, which will test, validate, and repair
00:14:34,080 --> 00:14:38,480
any system files that may have been replaced
by unofficial, and potentially buggy or slow,
00:14:38,480 --> 00:14:43,600
third party replacements.
With your system fully
updated, cleaned of junk files and malware, fully
00:14:43,600 --> 00:14:48,000
tuned and optimized for disk space, your system
is about as fast as it can be. Your much more
00:14:48,000 --> 00:14:52,160
drastic alternative is to clean-format the machine
and reinstall Windows, but that's a significant
00:14:52,160 --> 00:14:57,200
investment of your time. In some rare cases of
a machine where the software installations or
00:14:57,200 --> 00:15:02,240
configurations have been damaged extensively, it
might still be your best option and last resort!
00:15:02,880 --> 00:15:07,360
If along the way you found today's episode to be
any combination of entertaining or informative,
00:15:07,360 --> 00:15:10,400
I'd be honored if you'd consider leaving
a like and subscribing to my channel.
00:15:10,960 --> 00:15:14,400
If you have any interest in matters
related to Autism, Asperger's, or ASD,
00:15:14,400 --> 00:15:18,400
please check out my book on Amazon, Secrets
of the Autistic Millionaire. It's got nothing
00:15:18,400 --> 00:15:21,920
to do with money and everything to do with
living a successful life on the spectrum.
00:15:21,920 --> 00:15:26,320
It's everything I know now that I wish I'd
known back then.
Remember I'm mostly in this
00:15:26,320 --> 00:15:29,760
for the subs and likes, so please be sure
to leave me one of each before you go today.
00:15:29,760 --> 00:15:33,920
In the meantime, and in between time, I hope to
see you next time, right here in Dave's Garage.
28594
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.