>you don't need 16GB! >stick to 8GB, you won't

>>61367014
You don't need that much RAM unless you're doing something like video/photo-editing, in which case you should be at least intelligent enough to not believe anything you read on /g/.

Windows 10 was designed to use all your RAM, they call it caching

>>61367056
except there is clearly no cache used here

>>61367034
/thread

File: .png (16KB, 679x464px) Image search: [Google]

16KB, 679x464px

>>61367014
Talk about bloat
>>61367034
/thread

File: clearly no cache used.jpg (83KB, 1568x976px) Image search: [Google]

83KB, 1568x976px

>>61367095
>clearly no cache used here

>>61367014
>not noticing that his pleb C code has memory leacks

>>61367014
Looks like you're just running a stress test that uses most of your memory and maxes out your CPU

>>61367056
It only use 3 gb ram on Xbox.

Cool kids use 32 GB to be safe

>>61369109
You sure this is actually cache-on-ram?
Because I'm at 1.9 GB used, and it says 1.5 GB is "Cached".

It does say everything I'm running takes 0.4 GB, but surely there's windows services, drivers etc that takes *something*?

>>61367014
We're on /g/ right now and you told me to get as much RAM add i can afford. So should I listen to /g/ or what? Really makes me think

Cache itself might be a good argument for more ram or less.
If you use a LOT of files on your daily work, like,10GB+ of data you update per day, having a bunch of RAM to cache this data might be a good idea.

File: file.png (26KB, 637x692px) Image search: [Google]

26KB, 637x692px

>tfw fell for the 32GB ram meme.
Feels good though.
Made a Ramdisk for %temp% and pagefile. It's very convenient.

>>61367014
Ever thought of virtualization?

>>61368861
>kernel secret
please tell me!

>>61367014
/g/ also told you to not use Chrome you stupid fuck.

File: ramlet.png (42KB, 955x754px) Image search: [Google]

42KB, 955x754px

Honestly I should have gone with 4x16GB, but cheaped out because DDR4 prices are high.

>>61370451
>ramdisk for pagefile
kinda redundant don't you think?

but what's the performance increase from putting the temp folder on ram?

>>61370451
What's the 9gb cache suppose to help with?

>>61367014

void *s;
while(1) {
  s = malloc(1000000);
  if(!s) {
    printf("Look how much RAM I'm using\n");
    break;
  }
}

>>61370698
Some programs/gaymes won't work properly without a pagefile. I don't want it on my SSD (more writes) or HDD (slow speed).

>but what's the performance increase from putting the temp folder on ram?
May speed up some programs that use temp folder for cache (7zip for example). And I don't need to worry about all the shits that Wangblows and other programs throw in there).

>>61370805
>Some programs/gaymes won't work properly without a pagefile.
didn't know this

interesting

>>61367014
Don't know about you anon but my gentoo install uses around 150 mb of ram with firefox

>>61370569
>>61367014
What the fuck are you guys doing I can never get over 6 gb of ram even when doing something very autistic

>>61367014
>windows 10
/thread

>>61367014
Remember to not use javascript/electron based software

File: screenfetch-taeyeon-2017-07.jpg (90KB, 1254x334px) Image search: [Google]

90KB, 1254x334px

>>61367034
>You don't need that much RAM

yeah, most of the time you don't need 32 GB but it sure is nice to have it when you do.

>>61370843
yeah, I had to increase my pagefile to play arkham knight even though i got 16GB ram

~ $ node memory_leak 
/home/mike/memory_leak:1
(function (exports, require, module, __filename, __dirname) { void *s;
                                                                   ^
SyntaxError: Unexpected token *
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:389:7)
    at startup (bootstrap_node.js:149:9)

check mate C fags, bare metal nodejs protects you from memory leaks

>>61371387
>>61370779
i merely pretended not to be retarded

>>61368861
Lel, productive on plan9?

>>61371165
3 tabs open on chrome

>>61371165
I'm testing some DFT based quantum transport code I'm working on. It involves a few eigenvalue problems for (complex, double precision) matrices that are quite large, so that's why I'm using so much memory. For bigger problems I'd have to run it on the cluster, but working locally is just nicer when testing code (if possible).

>>61371587
Made me reply

>>61371806
Okay that doesn't sound like what your average fa/g/ would do
You need ram

Hmm, It looks like OP is using google chrome.

>>61367014
>99% ram usage
>100% cpu usage
I can do that with 64 gb of ram
your point is retarded

File: 2017-07-14_112627.png (35KB, 396x448px) Image search: [Google]

35KB, 396x448px

>JUST get 8 gb
>it's enough

I only have my browser open

>>61367014
>winblows 10
fucking retard

>>61369153
But the OS isn't a full Windows 10 OS