SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Rambus (RMBS) - Eagle or Penguin -- Ignore unavailable to you. Want to Upgrade?


To: unclewest who wrote (23340)6/23/1999 8:50:00 AM
From: Charles R  Read Replies (1) | Respond to of 93625
 
unclewest,

In your absence, the thread was telling me that you are the resident expert. What do you make of the following from Tom's?

www6.tomshardware.com

< Conclusion

It seems pretty obvious that Camino plus RDRAM is a very questionable solution right now. The performance increase over today's top of the line systems seems marginal, however the costs are exorbitant. Running Camino at 100 MHz FSB is even less sensible, because the CPU still corresponds with the system at the same speed as with BX. We users can demand more performance and a lot lower prices. This will have to happen until September 5, 1999, unless Intel wants to experience their very own Waterloo with Camino or 'i820'.

Looking at the benchmark results makes one thing perfectly clear. Right now the right solution would be a slightly modified BX-chipset that can divide the FSB by 2 so that the AGP can run at the desired 66 MHz whilst the FSB runs at 133. BX with PC133-support would be faster than any other x86-chipset that I've seen so far and it would be so easy to make this chipset reality. This won't happen though. Therefore we'll either need to wait until VIA or ALi supply us with a well performing solution of a PC133-platform, in case that'll ever happen, or we go ahead and shell out a significant amount of money for a Camino-platform plus RDRAM, without receiving a decent performance increase in return. It might be best sticking to BX altogether. >

Chuck