Slashdot Mirror
High Performance DDR2 Memory Breaks 1.25GHz
TrackinYeti writes "Performance PC Memory manufacturer, Corsair recently released a new addition to their flagship Dominator line of
desktop memory,
the
TWIN2X2048-10000C5DF. This 2GB DDR2 memory kit features the company's
DHX Dual Path Heat Xchange cooling technology, support for Enhanced Performance
Profiles (EPP), it includes one of Corsair's Dominator active memory coolers,
and it's rated for operation at a currently industry leading 1.25GHz."
Yes, it comes with A/C, but you may not need it. I'm running an 800Mhz version of this memory and they're not even warm to the touch.
Watercooling for memory is already available, check products from Koolance.
The basic structure of Dynamic RAM has not changed, it still takes about 50nS for row precharge (Tras
and 20bS column reads. All they've done is speed up the interface logic. The memory cell access is no faster.
OK, so once you've opened a row, you can read that faster, but how many operating systems are
optimized to keep the data row aligned in the system memory? You have a data request that is outside
of the row you've opened, you have to close that row and open another, 120nS penalty.
At 1.0GHz, that's 120 clock cycles.
Starman97@Gmail.com (bring it on spammers)
Actually, it's a question that has already been answered.
No trees were harmed in the posting of this message. However, a great number of electrons were terribly inconvenienced.
Actually, having the PC open from one side, you don't need a heater in the cold winter. And in the summer, you can use the heat to powerup a small refrigerator, so you can have your beers near to the computer.
By default, it lets processes overcommit memory. That means you can malloc more than there actually is. This is done with the expectation that programs allocate extra memory they don't actually use. Problem is that an excessive allocation succeeds, but then the system can't satisfy it, so it has to kill some random process.
Do this: This will turn off overcommit completely. When some program tries to request too much, malloc simply fails. No random processes get killed. The program that tired to allocate the memory is given a chance to handle the failure, unlike what happens with the default setting.
The Itaniums are up to 24MB, but the x86 quad cores are "only" up to 8MB total. The next generation Core processors will probably go up to 16.