<A HREF="http://www.amdmb.com/#News-4792" target="_new">Here's</A> a rumor from an AMD fan site (amdmb.com). New Athlons: 2400+ and 2600+ on a new improved revision of the .13 process. Plus the possibility of 333 FSB. Cool if it's true.
And also, I wonder why there's no a chipset maker who doesn't make Athlon chipset with RDRAM support??!
Just imagine something like nForce2 with RDRAM!
But right now, while Durons are the most valuable CPUs (Duron@850MHz+Elitegroup mobo=$75 in Bulgaria, maybe less in the USA and Asia), AMD are lagging in the high-end, high-speed sector, yeah?
but the AMD`s FSB`s wandwidth is (if FSB=133MHz) 2133mb/s so a faster ram wouldn`t really help(the nforce`s dual channel DDR didn`t really kick up performance)
amd needs to make chips with faster FSB, or use that quad-bus stuff used in p4, then rambus would really be effective.
by the way, u knwo about VIA`s apollopro266? it`s a p3 chipset, using DDR. p3`s FSB133 is 1066mb/s fast, while the DDR266 is twice as fast. the DDR didn`t have any benifits over the SDR pc133. so u see, the front side bus needs to be as fast as, or faster than the RAM speed.
While the added memory bandwidth may boost average performance a few percentage, the Athlon simply isn't that memory starved. AMD is not focusing on their K7 line as of right now, they're putting everything on Hammer. If they were to try to improve the K7 line most likely they'll try to ramp up clockspeeds as that is what's holding it back. You can put as fast a memory as you want and as much cache as you want but at 1.8 GHz, a CPU isn't going to eat up much of that.
Yeah, but at the same speed, say 1666Mhz, an Athlon with a 166Mhz FSB will have a nominal performance gain over an Athlon with a 133Mhz FSB. This effect is even more pronounced on the Pentium4, it practically THRIVES on cache and memory bandwidth.
The needed memory bandwidth and cache latency is almost directly (in fact, probably exponentially) related to clockspeed. Processors attempt to fetch and decode a certain amount of instructions per clock. To do this, you have to spend a lot of time looking at the data in the cache, in memory, prefetch (in the case of the P4 and Palomino), and of course, still have enough bandwidth left asside to keep the processor fed with incomming instructions every clock. The more clockcycles per second you have, the more instructions the processor will have to "sift through" in order to find instructions in which it can process independently. This is why huge amounts of bandwidth are needed.
The P4's higher clockrate means it will indeed need faster memory and lower latency cache in order to keep the processor fed. At 1.8 GHz, the current K7 line doesn't attempt to fetch that many instructions per second (although it does finish a bigger percentage of the ones it fetches per second than the current P4 design).
At 2.53 GHz, the availability of instructions is absolutely crucial to keeping the P4 pipelines filled. And as another post demonstrated, a hyperpipelined design will only be able to maintain relative IPC if the pipeline is filled at all times with useful instructions.
I strongly disagree. unfourtntly I dont have time to explain it now as im going to a movie with my friends (its Israel here so the time of day might seem alitle strange to you). I will give my explanation later.
This post is best viewed with common sense enabled
yeah, i read this in another newspaper in korea. seems not a rumor, though i think that the reporters over here translated the site u have linked up there.
I dont think they will. While a few DDR333 now support the divider for running 166FSB within spec, not all DDR333 boards do. And those that do dont officially support running at those speeds. By upping the FSB it would cater to such a small market, many Athlon users are still on the 133 and 266 chipsets and to upgrade thier CPU's they would require a brand new motherboard. I'm sure they would release faster 133FSB chips as well. But I think the 166 chips would only be for a very small market and probably wouldn't sell too well. It wouldn't make any sense to try to convert over to 166 when you have a new core coming around the corner.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.