Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?

To: Y. Samuel Arai who wrote (86089)	1/8/2000 11:45:00 PM
From: Process Boy	Respond to of 1572102

Y - Here is the disclaimer from the site where the rumor originated: lostcircuits.com General disclaimer: This page only reflects the author's personal opinion and assumes no responsibility whatsoever regarding any of the contents or any damages that may occur explicitly or implicitly from reading the contents of this site.

To: Y. Samuel Arai who wrote (86089)	1/8/2000 11:52:00 PM
From: Process Boy	Read Replies (2) \| Respond to of 1572102

Y. - As long as were posting BBS content, here's a neat little blurb I caught from JC's regarding Coppermine's cache: jc-news.com The latency of the L2 cache is not known to me, though it will likely be in the teens. The Celeron's L2 latency is something like 11 cycles, the K6-3 is 13ish cycles, the Katmai/PIII is 27 cycles, the K7 is 24 cycles (the newer two speed grades may have a slightly higher latency, for obvious reasons), *the Coppermine/PIII is 7 cycles* (this is an amazing, commendable, nearly impossible achievement, and it explains 90% of the way why the PIII is able to attain parity with the Athlon).** In my opinion (I am not an expert, but I pretend real well), Jedi's L2 latency will probably be along the lines of the K6-3's (that's just my WAG, though). PB

To: Y. Samuel Arai who wrote (86089)	1/9/2000 12:02:00 AM
From: Elmer	Read Replies (1) \| Respond to of 1572102

Re: "Hey don't shoot the messenger. I'm only passing on some information I found at JC's. Its too early to tell exactly what the problem may be without more info...it could be a problem with the chipset HP's using...it could be the Intel CPU... it could have been damaged during assembly by HP. I'm sure for the HP tech, Intel is an easy scapegoat for their customers... " The reason I jump on you is because some unknown person makes a wild ass claim on some obscure board and you post it as gospel. That's trash tabloid posting and it shows your standards are in the gutter. EP