[MUD-Dev] memory and speed
Caliban Tiresias Darklock
caliban at darklock.com
Thu Jun 10 21:30:17 CEST 1999
On 05:28 PM 6/10/99 -0700, I personally witnessed Matthew Mihaly jumping up
to say:
>
>We tripled our memory today, from 128 megs to 384 megs, but we seem to
>actually have slowed down. In fact, adding more memory has definitely
>slowed us down. Some tasks are taking nearly twice as long as before. This
>is extremely upsetting, to say the least. Anyone have any ideas?
I have a thought, but I don't know how relevant it is these days. I'm not
very hardware-literate anymore in terms of newer memory systems. All of
this is valid for older 72-pin and 30-pin SIMM and DIMM modules, but the
newer stuff I just don't have a lot of knowledge of.
Some (bad) cache implementations are really per-chip caches. So when you
stick a bigger chip into a slot -- like a 64 meg RAM chip instead of a 32
-- that cache gets fewer hits. It becomes less effective. When you spread
your RAM evenly across slots using minimum size chips to get the RAM you
need, that can mean faster performance. This is one reason why the same
motherboard may perform differently with a single 128 meg chip than it does
with two 64 megs or four 32 megs. Other cache implementations are even
worse, and "top out" -- they cache the first X megs of RAM, and that's it.
If your data is in the rest of RAM, your cache is missed entirely. I also
seem to recall that the first 512K cache machines really did a 256K cache
of the first 64 MB, and a 256K cache of the second 64MB... which was
actually pretty smart at the time, since the performance of a 256K cache
was within epsilon of a 512K cache on any given amount of RAM, and back
then 128 MB was an insane amount of memory anyway.
The thought process behind both of these is to match what PC manufacturers
are doing -- using lots of small RAM chips instead of one big one -- and
what users are doing, which is sticking a lot of RAM in the system that
they don't need. This actually works pretty well under Windows, but under
alternate operating systems it really bites. As a result, I'd probably go
to a hardware manufacturer who sold systems with my preferred O/S installed
than just grab something off the shelf and drop my favorite O/S on it. The
specialised manufacturer is likely to know things I don't about the MB I'm
getting, and to choose one that will work well for the O/S I'm installing.
Unless my favorite O/S happened to be Windows. Which, in my case, it sort
of is -- as long as I only have one computer running (other than my PS/2
XT, which will run DOS until it dies), it will be running Windows. But I'm
in the market for a couple more, so if you happen to have two old P60s and
a couple PII machines lying around... give me a shout. I'm also looking for
a good deal on a reasonably recent G3, if only so I can say I have one. ;)
-----
| Caliban Tiresias Darklock caliban at darklock.com
| Darklock Communications http://www.darklock.com/
| U L T I M A T E U N I V E R S E I S N O T D E A D
| 774577496C6C6E457645727355626D4974H -=CABAL::3146=-
_______________________________________________
MUD-Dev maillist - MUD-Dev at kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev
More information about the mud-dev-archive
mailing list