馃攳
Will More RAM Make your PC Faster?? (2020) - YouTube
Channel: unknown
[0]
- Since our last video on this topic,
[2]
a lot has changed.
[3]
AMD took the CPU core
wars to the next level.
[6]
NVIDIA turned RTX on
[8]
and Apple dropped the new Mac Pro.
[11]
But has RAM usage changed?
[13]
Do you, Wanda, really need
1 1/2 terabytes of RAM
[18]
or will just a dab do yah?
[19]
To find out, we tested
a variety of workloads.
[23]
Everything from opening
browser RAMs in Chrome,
[26]
(chuckles) excuse me, browser tabs,
[28]
to high resolution gaming,
[30]
to 4K video editing,
[32]
to complex Flow Simulation
[34]
on a single four-gig stick of RAM,
[36]
the smallest available for DDR4,
[39]
all the way up to a monstrous 256 gig kit
[44]
and everything in between.
[46]
And how much do you need?
[47]
Well, as always the answer is, it depends.
[52]
And as always, here's
a segue to our sponsor.
[54]
XSplit, XSplit makes
powerful streaming PC apps
[58]
for streamers, vloggers and more.
[60]
Check out their VCam app to
change or blur your background
[62]
without a green screen.
[64]
We're gonna have that linked below.
[65]
(bright music)
[75]
Just like last time,
[76]
we're gonna track page file usage
[78]
with performance monitor and open up tasks
[81]
until we notice activity in the page file.
[83]
That threshold where the system starts
[85]
to swap data out of RAM
[87]
and onto the boot drive is important.
[90]
Not because you would
instantly see your system
[92]
slow down to a crawl,
[94]
but because that's where
you could see a dip
[97]
in system responsiveness
when switching between apps
[100]
or even an increase in load times
[103]
for programs that have been paged
[104]
to your SSD or hard drive.
[106]
Before we begin though,
[107]
I wanna talk through one of
the most important choices
[110]
for a video like this.
[112]
For our CPU, we went with the
24-core AMD Threadripper 3960X
[118]
because it allowed us to test
[120]
every one of our RAM configurations
[122]
on the same ASUS Zenith
II Extreme motherboard,
[125]
eliminating that as a variable.
[127]
We also went with that
because we wanted a system
[129]
that was reasonably representative
[131]
of what will become available
to general consumers
[134]
over the next few years.
[136]
We could have plunked a 64-core processor
[139]
onto that same motherboard,
[140]
but that ain't going mainstream.
[143]
While the way things are going,
[145]
24-core actually might, thanks AMD.
[148]
We went with an RTX 2080
SUPER graphics card,
[151]
a Corsair MP600 1 terabyte boot drive
[153]
and a variety of Corsair
Vengeance Memory that was chosen
[156]
simply because Corsair has an
incredibly broad memory lineup
[159]
that covers any config we could want
[161]
and they sent it over to us.
[163]
At four gigabytes, everything
is about as you would expect.
[167]
We're sitting at around 50% usage
[169]
after logging into Windows
before we've even done anything.
[173]
Simply opening Chrome and
watching a 4k YouTube video
[176]
immediately pings the page
file crossing our threshold.
[180]
If you avoid video,
[181]
the good news is that you
can open six to seven tabs
[183]
of various text and image-based sites
[185]
before you see page file use
[187]
and we got to about 125 tabs
[190]
before Chrome decided it had had enough
[192]
and completely pooped itself.
[194]
Eight gigs was much better.
[197]
We comfortably handled
three 4K videos from YouTube
[200]
and 27 tabs at the same time
[203]
before we saw any page file usage.
[205]
630 tabs later, we saw the
system become unresponsive
[209]
and laggy anytime we tried
to load or reload a page.
[212]
Maybe on Linux, four gigs would be okay,
[215]
but eight gigs looks like
the lowest we'd recommend
[217]
for a good Windows 10 experience.
[220]
With 16 and 32 gigs,
[222]
we stuck with the three 4K YouTube videos,
[224]
you can only watch so many
videos at the same time,
[227]
and made it to 430 and 730
other tabs respectively
[231]
before tapping that page file.
[233]
Now Chrome wasn't very happy
[234]
when we hit our max tabs in either case,
[237]
but as long as we didn't
touch anything else,
[239]
the computer was actually still usable.
[242]
It's safe to say that anything beyond this
[244]
is pretty much colossal overkill.
[246]
Onto the games.
[247]
Shadow of the Tomb Raider
calls for eight gigs of RAM
[250]
for its minimum spec and 16
for its recommended spec.
[254]
Rainbow Six Siege wants
six gigs of RAM minimum
[257]
and only eight gigs recommended.
[258]
And finally, we've got CS:GO
[260]
that needs just two gigs of RAM, just two.
[265]
You can basically run on
overclocked potato at this point.
[268]
All of our games were ran at
1440p in the highest settings
[272]
with no motion blur, obviously.
[273]
Starting at four gigs of RAM,
[275]
CS:GO (chuckles) as advertised
[278]
ran just fine at 278 frames per second
[280]
with no noticeable issues.
[282]
But while both Tomb Raider
and Siege seemed to run well
[287]
at 90 and 154 FPS respectively,
[290]
what's interesting here is that
these great looking numbers
[293]
did not translate to a
great gameplay experience
[297]
due to occasional frame rate dips.
[300]
Both games reached about
60% page file usage,
[303]
so I think we know what to blame.
[304]
Tomb Raider jumped to 103 FPS
[307]
when we switched to eight gigs of RAM
[309]
and smoothed out considerably
[311]
with almost no stutters
or hitching to be seen.
[313]
And Rainbow Six also improved to 155 FPS,
[318]
so okay, not really.
[319]
But just like Tomb Raider,
[321]
all the stuttering was gone.
[323]
CS:GO added a whopping six frames.
[326]
But sarcasm aside, it
was a solid experience
[328]
with no issues as we'd expect.
[330]
So eight gigs then is
still plenty for gaming?
[333]
Well, here's the thing.
[335]
On a sanitized benchmarking
Windows install,
[338]
nothing else is gonna be
running in the background.
[341]
That's not representative
of the real world.
[343]
And when Tomb Raider
and Siege were running,
[345]
they were using seven to 7 1/2 gigs of RAM
[349]
and the page file hit
20% usage on occasion.
[352]
So having Chrome, Discord,
[354]
and or a music app open in the background
[356]
would likely affect
performance to some degree.
[359]
Fortunately, moving up to 16 gigs
[361]
gives us plenty of room to work with.
[363]
Just like there's plenty
of room in your closet
[365]
for our merch, lttstore.com.
[366]
Average frame rates either
stayed steady or improved
[369]
and we had plenty of headroom
to record our gameplay
[372]
or stream in the background.
[373]
Past this point though,
[375]
there was no real
performance gain or loss.
[377]
Adobe Premiere cut four and
eight gigs down pretty quick
[381]
with the four-gig setup
crashing on a regular basis
[384]
anytime we tried to render
just a one-minute test clip.
[386]
And as for our eight-gig config,
[388]
it did manage to render the clip
[390]
but it took a hot minute, as the kids say.
[393]
The video that we're using
is a mix of edited 4K
[396]
and 8K footage from
one of our past videos.
[399]
At 16 gigs, Premiere was usable
[401]
with our render taking just
three minutes and 23 seconds
[404]
but scrubbing and playback
[407]
was like watching an
old movie picture real.
[409]
Remember guys, this is on a Threadripper
[411]
and at both 1/4 and 1/8 scale.
[415]
So we'd say this is okay
[417]
as long as you're willing to wait around
[419]
to create proxies before you edit.
[421]
So those are lower resolution
versions of your clips
[424]
or if you stick with 1080p.
[426]
32 gig and beyond
[428]
is gonna help bring your
render times even lower
[430]
and work with much larger
[432]
and more complicated project files.
[434]
A lot of the usage here
though is gonna come down
[436]
to your individual workflow needs.
[439]
Our editors, Mark and A.Prime
[440]
have slightly different machines.
[442]
With Mark's having 64 gigs of
RAM and Prime's having 128.
[446]
Both of them have Premiere, After Effects,
[448]
Photoshop, Chrome, Word and Excel open
[450]
while editing a video
[452]
and depending on the video,
[453]
Mark will see 85 to 95%
usage while he edits
[456]
and A.Prime will see 60 to 70%
[459]
sometimes spiking to 90%
utilization or 115 gigs.
[464]
Now up until this point in the video,
[466]
I would forgive you for
thinking that 256 gigs
[469]
is overkill for anything.
[471]
But while nothing that
average folks are likely to do
[474]
will ever touch it,
[475]
engineers and scientists
[477]
will often have huge
amounts of data to deal with
[481]
to the point where such a system load-out
[483]
might not even be a luxury,
but rather a necessity.
[487]
Check out our RAM Punisher
Flow Simulation benchmark.
[491]
The more memory you have,
[492]
the more variables you can account for,
[494]
improving the airflow calculations
[496]
around this Cybertruck model.
[498]
This thing can easily
suck up 256 gigs of RAM
[503]
and actually prefers to have more.
[506]
Shout out to Flow Joe, by
the way, for this benchmark.
[508]
Another example is a
professional composer and mixer
[511]
like Neil Parfitt,
[512]
who regularly has projects
reach upwards of 215 gigs
[517]
thanks to all of the tracks
[518]
and instrument sets that he needs loaded.
[520]
Having them in memory
means instant access.
[523]
Now one thing our test was
not able to account for today
[526]
was the increase in memory bandwidth
[529]
as we scaled from single channel to dual
[531]
and quad channel configurations.
[533]
That's why we focused page
file usage as our threshold
[537]
rather than on the
performance differences.
[540]
But stay subscribed
because that is something
[543]
that we would like to
explore going forward.
[545]
So then in the end, conclusion.
[548]
You're probably fine
[549]
with just a solid eight to 16 gigs of RAM
[552]
for your everyday use and gaming.
[554]
If you do photo and video editing,
[556]
bump that up to 32 or 64 or 128
[559]
if you do it professionally.
[561]
And beyond that, well, it's
probably just bragging rights
[564]
unless you know for a fact
[565]
that you're doing something
that benefits from it.
[569]
Which we're not judging.
[571]
Bragging rights is okay too.
[573]
Just like you'll have bragging rights
[574]
by switching to our sponsor, XSplit.
[577]
XSplit VCam allows you to remove, replace,
[580]
and blur your background
without a green screen.
[582]
It works with any webcam
[584]
and there's no need for
complicated lighting setups.
[587]
It uses AI to automatically
know the difference
[589]
between you and your background
[591]
and allows you to
customize your background
[593]
to anything you want.
[594]
VCam works with other
XSplit broadcast tools,
[596]
but also OBS, Slack,
Hangouts, Skype, and more.
[600]
And they've got 24-7 support
with lifetime updates.
[603]
It costs as little as
9.95 US for three months
[606]
and a lifetime license is
available for just $40.
[610]
Use offer code, LINUSTECHTIPS.
[611]
We're gonna have that
down below to get 10% off.
[614]
All right, if you guys
like crazy RAM videos,
[616]
maybe check out our recent one,
[618]
opening up Chrome tabs
[619]
on a system with two terabytes of ride.
[622]
It's a wild and sometimes
very tedious ride.
[626]
But don't worry, we cut out the tedium.
[627]
It's just, it's a fun video.
[629]
Stop, what do you people want?
[632]
Everybody's messaging me.
Most Recent Videos:
You can go back to the homepage right here: Homepage