Personal computing discussed
Moderators: renee, Flying Fox, Thresher
GrimDanfango wrote:True, for pure gaming, 8GB is more than you'll need for now. Most games haven't even made the transition to 64-bit yet, so as I understand it they can't even address larger than 4GB as a single process. Unless you're planning to run two games at once, 8GB is fine.
Savyg wrote:I haven't seen Warframe use over ~3GB of RAM, oddly. Then again, the whole game is only like 4GB. Hehe.64 bit gaming is due this year from EA I've heard, though I don't know if I believe it...we'll probably find out at E3 what's going on. Warframe and WoW have a 64 bit client...don't know what the actual usage pattern is for them though.
Won't see major uptake in 64 bit gaming on PC until the PS4 has been out a bit IMO.
Forge wrote:32bit Windows apps give a 2GB/2GB app/kernel split to the mem map. That was one of the awesome things about going X64, you can give different "complete" 4GB memory maps to different apps.
Using >2GB for one app means you're on X64 or are running a bad and poorly documented Windows kernel option...
I had a point. I'll go find it.
Krogoth wrote:"Kernel option" makes me think he's referring to PAE, rather than LAA, although PAE is neither "bad" nor "poorly documented". PAE isn't that useful for a single app, though, since as you mentioned Krogoth, a single app can only use 3GB per process (with LAA; 4GB is only for 32-bit LAA apps on 64-bit OS.)Forge wrote:I believe you are referring to the "Large address space aware" flag that you can pull on 32-bit applications in Windows x64. It will allow the 32-bit application to utilize up to 4GB per process instead of the normal 2GB limit.Using >2GB for one app means you're on X64 or are running a bad and poorly documented Windows kernel option...
MadManOriginal wrote:The 8GB I have now is that sweet Samsung low profile/low voltage that also overclocks like mad. The mobo is limited to DDR3-1600 though (at least without XMP) so I have it running DDR3-1600 CAS8 at 1.40V.
auxy wrote:Krogoth wrote:"Kernel option" makes me think he's referring to PAE, rather than LAA, although PAE is neither "bad" nor "poorly documented". PAE isn't that useful for a single app, though, since as you mentioned Krogoth, a single app can only use 3GB per process (with LAA; 4GB is only for 32-bit LAA apps on 64-bit OS.)Forge wrote:I believe you are referring to the "Large address space aware" flag that you can pull on 32-bit applications in Windows x64. It will allow the 32-bit application to utilize up to 4GB per process instead of the normal 2GB limit.Using >2GB for one app means you're on X64 or are running a bad and poorly documented Windows kernel option...
Forge wrote:PAE is wonderful, but Microsoft didn't want to support it on desktop OSes since it would cannibalize the push to x64.
Krogoth wrote:PAE is dead get over it.
Krogoth wrote:PAE is dead get over it. It was a hack done out of necessity when 64-bit hardware didn't exist in x86 realm and high-end enterprise servers needed more than 4GB of memory. x86-64 made it completely obsolete for the x86 crowd. Microsoft and *nix crowd moved on with the times and dropped it once x86-64 hardware became commonplace on the enterprise-front.
Krogoth wrote:PAE is dead get over it. It was a hack done out of necessity when 64-bit hardware didn't exist in x86 realm and high-end enterprise servers needed more than 4GB of memory. x86-64 made it completely obsolete for the x86 crowd. Microsoft and *nix crowd moved on with the times and dropped it once x86-64 hardware became commonplace on the enterprise-front.
PAE required drivers that were aware of it (limited to enterprise-level hardware that used it) and you took a performance penalty on its usage (5-15% CPU utilization back then, probably 1-2% on current CPUs). There's no point in using it these days. Get x64 hardware and OS if you want to use more than 3-4GB of memory. The fastest, purely 32-bit hardware for x86 was first-generation Prescotts (Pentium 4) and Barton-based Athlon XPs.
MadManOriginal wrote:Nice! I run G.SKILL ARES, which is cheap stuff rated at DDR3-1866 1.5v CL9; mine seems to run fine at 1.4v! I prefer to run it at 1.55v and CL9 1T tho.The 8GB I have now is that sweet Samsung low profile/low voltage that also overclocks like mad. The mobo is limited to DDR3-1600 though (at least without XMP) :( so I have it running DDR3-1600 CAS8 at 1.40V.
kumori wrote:Hehe, the ARES does have pretty heatsinks, but they're really small; they barely add to the size of the RAM itself. Mine are blue, but they come in a variety of colors. (The blue matches my Gigabyte mainboard nicely!)I love this RAM. I think more people should consider it instead of the "gaming" RAM even though it lacks ersatz heat sinks.
auxy wrote:I was going to make a snarky remark about mis-using the word ersatz, but it turns out I'm the one who didn't realize what it meant. "You keep using that word ... it doesn't mean what I think it means!"
auxy wrote:"You keep using that word ... it doesn't mean what I think it means!"[/sub]
Forge wrote:thats_the_joke.jpg (* ̄Oノ ̄*)You keep using that word... I do not think it means what you think it means. [/Inigo.Montoyo]
Nec_V20 wrote:You can dump your virtual memory there and also your browser cache and other temporary files.
No more mysterious problems created by a corrupted <pagefile.sys> is one of the main benefits I have found.
I don't think I've ever seen (that I'm aware of) "mysterious problems caused by a corrupted pagefile.sys".
just brew it! wrote:Linux certainly has aspects that drive me nuts too. The whole desktop environment ecosystem for the past couple of years, for example (pretty sure I've ranted about this before). But it tends to get the underling infrastructure right.
My Johnson wrote:I guess it is cheap but it's not cheap enough for me to have 32BG's.