Mo RAM, Mo Problems (2025)

Discussion (5 Comments)Read Original on HackerNews

Cockbrand•about 2 hours ago

Around the turn of the millennium I had a Sony Vaio 505TX, which had the same chipset. My machine was running Linux, and I maxed it out to 128MB RAM.

There was a kernel patch for this chipset back then, which treated all memory above the lower 64MB as a RAM disk, which could then be used as swap space.

This prioritized the faster portion of RAM while still having very fast swapping.

HerbManic•about 2 hours ago

It is funny to see how these older machines perform at their higher end limits. I'm guessing the idea on this was that if you needed that much RAM, the sacrifice of L2 cache was a worth while trade off.

It was only a few weeks ago that I found out the original BeBOX computers would switch off L2 cache when running in dual CPU mode. It was just a limitation of the memory controller. Again, the thinking of, if you need the extra compute over memory bus it would be a worth while trade off.

hypercube33•11 minutes ago

Honestly asking though is it worth that trade off? I enjoy watching people benchmark older Intel x86 based chips and without cache they are frankly awful slow. I'm not sure two without cache beat one with. The BeBox did run a totally different processor though so I have zero domain knowledge for that which is why I'm genuinely curious.

hsbauauvhabzb•about 2 hours ago

Many modern apps seem to cache based on total ram installed, and don’t seem to scale well to larger than normal systems. Chrome, I’m looking at you.

MrBuddyCasino•about 2 hours ago

My 1997 mainboard had extensible tag-ram, if I remember correctly. Perhaps this is the issue?

Mo RAM, Mo Problems (2025)

⚡ Community Insights

Discussion (5 Comments)Read Original on HackerNews