• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

When is RAM too much?



<< That problem was pretty much solved with on die L2 cache, before that it was chipset dependant. >>



This problem affected Intels socket 7 chipset (can't remember the whole name, beleived it ended in LX). Other than that one exception (memory > 64MB slowed the system down) the general rule is more memory will only speed your system up. Of course for the average user the benifit begins to level off at a certain point as you can easily end up having more memory than you can use, but certainly in the world of the high end, more memory always equals more preformance.
 
for win9x/me, dont go above, uh, 512 I think. But then again, if you have a lot of ram and want a good system, you shouldn't be running 9x anyway 😉
 


<< This problem affected Intels socket 7 chipset (can't remember the whole name, beleived it ended in LX). Other than that one exception (memory > 64MB slowed the system down) the general rule is more memory will only speed your system up. Of course for the average user the benifit begins to level off at a certain point as you can easily end up having more memory than you can use, but certainly in the world of the high end, more memory always equals more preformance. >>



It affected the entire 430*X line at 64MB with the exception of the NX and HX when equipped with 512kB L2 cache (w/ TAGRAM). It also affects the Ali5 (at 128MB). Putting a K6-2+, K6-3, or K6-3+ allows you to cache the maximum amount of RAM that the chipset can handle. This is due to the on die L2 cache.

...yes, I have seen the effects, it is VERY noticable.
 


<< oh, and don't get more than 4 gig 😉
(its a joke. 32-bit can only address 4 gig unless you work magic) >>



Current generation x86 32bit CPU's have a 36bit memory bus allowing them to address up to 64GB however accessing this much in code becomes messy.
 


<<

<< oh, and don't get more than 4 gig 😉
(its a joke. 32-bit can only address 4 gig unless you work magic) >>



Current generation x86 32bit CPU's have a 36bit memory bus allowing them to address up to 64GB however accessing this much in code becomes messy. >>



yeah, the linux kernel has a special option for boxes with >4gig
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top