WEBVTT

00:00:00.080 --> 00:00:05.520
don't lie you filled that nice squeaky clean

00:00:03.760 --> 00:00:11.920
Windows installed with garbage didn't you oh i get it you wanna chat with your

00:00:08.720 --> 00:00:14.880
friends and download games and edit

00:00:11.920 --> 00:00:19.520
videos but did you ever stop to think that all those things could be killing

00:00:16.800 --> 00:00:23.840
your FPS now of course everyone knows that having programs open

00:00:21.840 --> 00:00:28.640
in the background consumes system resources so it stands to reason that a

00:00:26.560 --> 00:00:32.719
lightweight Windows install should perform better but do you need to be

00:00:30.880 --> 00:00:36.719
concerned about that if you have a modern system well in this video

00:00:34.800 --> 00:00:41.440
sponsored by seasonic we'll be finding out exactly what sort of effect all the

00:00:39.760 --> 00:00:45.600
junk you might have running in the background will have on your gaming

00:00:43.600 --> 00:00:50.320
performance and you should get rid of it and if getting

00:00:47.120 --> 00:00:50.320
rid of it will even fix the

00:00:56.840 --> 00:01:01.760
problem in order to a b test anything

00:00:59.920 --> 00:01:06.080
you need to eliminate as many variables as possible that makes setting up our

00:01:03.760 --> 00:01:12.400
test here a little bit tricky because here's the thing even two identical

00:01:08.880 --> 00:01:14.799
model cpus or gpus can have marginally

00:01:12.400 --> 00:01:20.000
different performance characteristics so that means that every one of our

00:01:16.799 --> 00:01:22.799
benchmarks needs to be run on exactly

00:01:20.000 --> 00:01:29.040
the same hardware not just the same spec hardware down to even our seasonic prime

00:01:25.759 --> 00:01:31.200
tx1000 power supply this puppy sick by

00:01:29.040 --> 00:01:36.799
the way modular interface super quiet fan and 80 plus titanium efficiency

00:01:33.920 --> 00:01:41.600
the only non-identical part is our boot drives we've got a pair of crucial

00:01:39.520 --> 00:01:44.799
1 terabyte ssds we're gonna have the full details of our bench and our

00:01:43.040 --> 00:01:48.399
affiliate links down below the hardware is not the story today though where

00:01:46.399 --> 00:01:51.439
things get really interesting is in software

00:01:49.600 --> 00:01:57.040
both of our drives were configured with a fresh install of Windows 10 then we

00:01:54.000 --> 00:02:00.240
applied identical update regimens that

00:01:57.040 --> 00:02:02.799
is where the similarities end the clean

00:02:00.240 --> 00:02:08.479
build got only what was required for operation system drivers steam uplay

00:02:05.840 --> 00:02:13.360
epic games launcher and NVIDIA's GPU drivers plus chromium for a light-ish

00:02:11.360 --> 00:02:17.599
internet browsing experience oh and 7-zip because you need to unzip stuff we

00:02:15.760 --> 00:02:21.920
then went a step further and installed win arrow tweaker it's a super cool

00:02:19.760 --> 00:02:26.239
little tool that bricks Windows ability to phone home aka telemetry as well as

00:02:24.720 --> 00:02:31.360
putting a stop to things that most people don't need like cortana Windows

00:02:28.480 --> 00:02:36.000
inc workspace task view and the like it also attempts to intercept Windows

00:02:33.360 --> 00:02:41.519
updates before they are forced on the pc like the Windows malicious software

00:02:37.920 --> 00:02:43.120
removal tool a notorious resource hog

00:02:41.519 --> 00:02:47.440
as for the dirty build it's downright filthy we've got multiple

00:02:45.599 --> 00:02:51.920
pieces of security software fighting for resources then we've got skype discord

00:02:50.000 --> 00:02:56.000
spotify share x logitech gaming software course our iq steam ubisoft connect epic

00:02:53.760 --> 00:02:58.319
games launcher it's a lot of stuff

00:02:57.519 --> 00:03:03.200
and the craziest part is that it's not that

00:03:00.800 --> 00:03:06.959
crazy and these are all things that a normal gamer could easily have running

00:03:05.519 --> 00:03:11.280
behind the scenes to add a little bit of a dynamic load

00:03:08.959 --> 00:03:15.760
we're also throwing a 4k video on youtube running in the background

00:03:12.560 --> 00:03:19.040
because i heard zoomers are super into

00:03:15.760 --> 00:03:20.959
multitasking let's start then with idle

00:03:19.040 --> 00:03:26.080
loads as a baseline that was a snappy boot up

00:03:23.200 --> 00:03:31.360
and task manager has us pulling a grand total of

00:03:28.000 --> 00:03:34.959
one percent CPU of which point two we

00:03:31.360 --> 00:03:37.120
are at zero percent CPU usage

00:03:34.959 --> 00:03:40.239
not too shabby i don't know if i've actually seen that

00:03:38.959 --> 00:03:45.280
before zero percent CPU

00:03:42.239 --> 00:03:48.159
what's up with our RAM at and for memory

00:03:45.280 --> 00:03:51.840
we're sucking back a whopping 2.3 gigabytes

00:03:49.440 --> 00:03:56.480
not much else to say other than damn that's clean time to see the dirty boy

00:03:54.879 --> 00:04:02.239
by the way yes we know we're not using the gen 4m.2 slot it's a gen 3 drive

00:03:58.879 --> 00:04:04.239
it's fine there it is oh you know what

00:04:02.239 --> 00:04:07.599
it's the coating on the screwdriver tip colin ah that's why i wasn't able to

00:04:06.400 --> 00:04:12.239
short it before the store.com actually it's going to be

00:04:10.000 --> 00:04:17.040
wan hoodies before we have screwdrivers like that available v2 baby

00:04:14.720 --> 00:04:21.440
got pockets for days that's a dirty welcome

00:04:19.120 --> 00:04:25.120
all right oh god the microsoft store is still here got some malwarebytes down

00:04:23.360 --> 00:04:28.639
here i mean to be clear when we said it was going to have bloat we didn't mean

00:04:26.560 --> 00:04:33.199
like bad bloat having malwarebytes on your computer's perfectly legit thing to

00:04:30.400 --> 00:04:38.639
do oh god Corsair device update what the hell is glary utilities calling i just

00:04:36.160 --> 00:04:45.360
clicked all the boxes on nine night you know all things considered

00:04:42.160 --> 00:04:47.040
not that bad in terms of CPU usage

00:04:45.360 --> 00:04:51.520
anyway only about two percent

00:04:49.040 --> 00:04:56.240
but memory is an entirely different story we were sucking back over five

00:04:54.479 --> 00:05:00.080
gigs of memory now that's more than double what we were doing with our clean

00:04:57.759 --> 00:05:04.880
machine now the obvious answer to this is just to install more RAM but most

00:05:02.800 --> 00:05:11.440
people these days are running 16 gigs and buying more RAM costs a lot more than

00:05:08.720 --> 00:05:16.560
closing some background programs okay this is not staying at necessarily two

00:05:14.240 --> 00:05:21.600
sometimes around three there it is it's at three now four five

00:05:20.320 --> 00:05:25.680
wait what do you mean what is Windows explorer doing i don't even have it open

00:05:24.160 --> 00:05:30.400
now we've reached the point in the video where i have to do a little

00:05:28.880 --> 00:05:35.600
taste test and see can i tell the difference between the

00:05:33.440 --> 00:05:38.880
clean drive and the dirty drive i'm gonna go sanitize this i'll be right

00:05:37.039 --> 00:05:41.840
back let's try two different games and then i'll i'll try and tell the

00:05:40.160 --> 00:05:44.800
difference between them so i think the thing that you would have

00:05:43.280 --> 00:05:48.960
the hardest time knowing the difference between is like csgo or doom because

00:05:46.639 --> 00:05:52.880
they're already like 350 FPS why don't we do

00:05:50.840 --> 00:05:57.280
hitman i think there's like a zero percent chance Linus gets this without

00:05:54.800 --> 00:06:01.039
an FPS counter oh

00:05:58.720 --> 00:06:05.600
okay okay all right uh i will go away and

00:06:04.000 --> 00:06:08.479
then you either will or won't switch it i guess yes

00:06:10.400 --> 00:06:13.360
opening window

00:06:15.840 --> 00:06:21.280
i have my guess okay i say this is clean and the

00:06:19.120 --> 00:06:26.479
previous one was dirty that is exactly wrong i'm disappointed in

00:06:23.919 --> 00:06:31.680
myself my family um all my friends my supporters really

00:06:29.520 --> 00:06:35.680
let us down it's the opposite of an acceptance speech

00:06:33.440 --> 00:06:39.600
a rejection speech here's the thing though just because i can't tell the

00:06:37.600 --> 00:06:44.639
difference by hand doesn't mean that there is no difference so we did our

00:06:42.639 --> 00:06:48.960
homework and ran both of our setups through a gauntlet of benchmarks

00:06:46.319 --> 00:06:52.720
starting with synthetics in 3dmark time spy we were

00:06:50.560 --> 00:06:56.880
within margin of error i think it's fair to call this a tie but moving on to

00:06:54.639 --> 00:07:02.160
blender's classroom render we actually saw a significant gap with the render

00:06:59.440 --> 00:07:06.960
taking an additional 14 seconds on our dirty machine that's about three percent

00:07:04.560 --> 00:07:11.720
we then saw a similar story for browser bench's javascript based speedometer 2.0

00:07:10.240 --> 00:07:17.599
which netted a 4.25 reduction in performance on our

00:07:14.800 --> 00:07:22.080
dirty machine the results then tipped even further in our in-game tests with

00:07:20.000 --> 00:07:26.880
cs go seeing our greatest difference with a 5

00:07:23.599 --> 00:07:28.479
drop in FPS now to be clear that is

00:07:26.880 --> 00:07:33.120
still not the kind of thing that you're just going to be able to feel using the

00:07:30.960 --> 00:07:39.840
machine especially when you're pushing over 300 FPS but it is measurable

00:07:37.599 --> 00:07:44.319
f1 was tighter only a two and a half percent drop and we saw a similar story

00:07:41.759 --> 00:07:49.120
with hitman 3 in both the dartmoor and dubai canned benchmarks so across the

00:07:47.039 --> 00:07:53.919
board the loss was minimal but measurable and there are two main

00:07:50.639 --> 00:07:56.240
takeaways here one is that the more over

00:07:53.919 --> 00:08:01.120
spec your machine is the less likely you are to feel any kind of problem if we've

00:07:59.120 --> 00:08:05.440
been running eight gigs of RAM and a quad-core CPU we might have seen very

00:08:03.599 --> 00:08:10.240
different results maybe that's a good experiment for another day

00:08:07.199 --> 00:08:13.120
the second takeaway is that even with an

00:08:10.240 --> 00:08:16.879
overspec machine your background tasks are acting as a drag on your gaming

00:08:15.120 --> 00:08:20.639
performance i mean we didn't put this in the script because we didn't know yet

00:08:18.160 --> 00:08:27.840
but it's funny to see about a three percent difference in performance with

00:08:22.879 --> 00:08:27.840
about three percent CPU usage at idle

00:08:28.160 --> 00:08:35.440
so bottom line you need to keep an eye on it about half of you today are

00:08:32.399 --> 00:08:38.240
running 16 gigs of RAM or more which is

00:08:35.440 --> 00:08:43.599
great today but as your background programs get more resource intensive as

00:08:40.800 --> 00:08:47.920
they're apt to do that might change hopefully ddr5 with its faster speeds

00:08:46.000 --> 00:08:51.040
not to mention greater capacities is gonna bring some respite we've actually

00:08:49.600 --> 00:08:54.480
got some content in the works around that so make sure you get subscribed so

00:08:53.120 --> 00:09:00.720
you don't miss it now what i want to do is see if we can

00:08:57.519 --> 00:09:02.480
get some of that lost performance back

00:09:00.720 --> 00:09:06.080
so what's the best one to run probably cs go then right since that's where we

00:09:04.399 --> 00:09:11.279
saw the greatest difference yeah why not let's start let's start closing shiz

00:09:09.040 --> 00:09:16.480
see you later onedrive see you later dropbox oh god bye

00:09:14.240 --> 00:09:21.360
everything so is it as simple as that and we get all of our CPU back

00:09:18.480 --> 00:09:25.360
oh no Corsair still has services running in the background who else does we're

00:09:23.360 --> 00:09:28.000
down to only one percent CPU usage though

00:09:26.480 --> 00:09:32.800
okay well we should be able to see that it's time

00:09:30.399 --> 00:09:36.120
three two one scroll lock

00:09:36.720 --> 00:09:45.120
here we go point of clarification our benchmarking was all run at 1440p for 10

00:09:42.080 --> 00:09:47.760
40. 410 40. how close are we okay so in

00:09:45.120 --> 00:09:52.080
our benches dirty like fully dirty was 403

00:09:49.360 --> 00:09:57.440
222 now so we've picked up seven FPS the clean build

00:09:54.640 --> 00:10:00.640
was 423. it looks like just closing stuff wasn't enough and when arrow

00:09:59.040 --> 00:10:04.800
tweaker is actually contributing to a difference in our

00:10:02.880 --> 00:10:07.120
performance here yeah what do we have still running in the background that's

00:10:05.920 --> 00:10:11.040
pretty cool i mean there's still like anti-malware services sitting there

00:10:09.040 --> 00:10:14.640
drawing point four percent sometimes Corsair service is still running in

00:10:12.720 --> 00:10:19.040
spite of the fact that i closed the actual tray application you wanna just

00:10:16.640 --> 00:10:23.440
try force closing those things yeah we could try it dropbox service is

00:10:21.200 --> 00:10:28.320
still running dropbox update it's still running everything search still running

00:10:26.079 --> 00:10:31.839
like a lot of this crap is still running okay so we further trim the fat do you

00:10:30.079 --> 00:10:36.720
want to go check it again iq started again iq service for MSI

00:10:34.640 --> 00:10:40.560
motherboard i think wait the lg hub updater started again let's see if we

00:10:38.480 --> 00:10:47.440
can pull another couple FPS out of that let's try it one more time borrow 864.

00:10:43.839 --> 00:10:49.120
we got nothing more it's even less yep

00:10:47.440 --> 00:10:53.279
the good news is this benchmark is really consistent so

00:10:51.200 --> 00:10:57.760
it tells us that our our difference between clean and dirty is real

00:10:56.000 --> 00:11:01.440
and also tells us i think we're pretty much done here rather than to thank

00:10:59.279 --> 00:11:05.360
seasonic seasonic power supplies whether you got a clean rig or a dirty rig they

00:11:03.600 --> 00:11:08.560
have got the power for you they've got everything from

00:11:06.959 --> 00:11:12.160
value power supplies all the way up to ones with insane 12-year freaking

00:11:11.040 --> 00:11:17.120
warranties on them and all the performance that you could need you can check them out at the link in the video

00:11:15.600 --> 00:11:22.320
description if you guys are looking for another video to watch hey maybe check

00:11:19.200 --> 00:11:24.480
out the does a faster SSD matter for

00:11:22.320 --> 00:11:30.720
gaming video that we did a while back we tried everything from a SATA SSD to a

00:11:27.600 --> 00:11:32.640
top spec NVMe SSD and did a blind test

00:11:30.720 --> 00:11:35.519
to find out if our gamers could tell the difference