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.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Process Boy who wrote (71012)9/4/1999 3:35:00 PM
From: Tenchusatsu  Read Replies (1) of 1574997
 
<Nobody sandbags already made CPU's.>

The argument here is a notion that since Intel's CPUs were becoming too fast for the market to bear, they had to underclock their CPUs and put a multiplier lock on them to prevent overclocking. The overclockability of the Celeron 300A upon its release is their main piece of evidence. Now people think that it's AMD's turn to do the same, given that the third-party web sites like Herr Uberclockermeister are running their Athlons at 750 MHz.

The argument, however, falls apart when you consider a statement I've repeated over and over again, "It's the volumes, stupid!" There's no way AMD can afford to sandbag the numbers when their volumes are so low and demand is so high. Given that they can't produce more than 200K or 300K Athlons this quarter, I'm sure that AMD will find more than that many people who are willing to buy the fastest speed possible, even if it costs hundreds of dollars more.

The existence of the 550 and 600 speed grades, plus the non-availability of 650, tells me that AMD isn't yet able to reach those high speeds consistently. To tell you the truth, though, I don't know why people are finding the Athlon so overclockable. If AMD is truly sandbagging, then they are making a mistake.

Tenchusatsu
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext