harris1986 said:anyone know how much cache the am2 chips have got?
Exactly the same as their Socket 939 counterparts. The X2 5000+ has 512k per core however and the FX-62 has the standard 1MB per core.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
harris1986 said:anyone know how much cache the am2 chips have got?
mcmad said:People really need to get away from the idea that a smaller CD process will bring magical results, they simply wont, going from 90nm to 65nm will allow a higher clock speed & possibly more cache on board but thats all, its not a new architecture, its just allows a speed bump. Once a few people get AM2 under phase change that will give you an indication of whats to come from AMD.
The reason Conroe is looking unbeatable at the moment is nothing to do with the process CD its just that Intel are coming back big time with what looks like a cracking design (fingers crossed the real performance is as good as we are seeing so far).
funny thing is AMD will have to crank up the speed to compete.. nice role reversal coming up..
Corasik said:AMD dont seem to be increaseing the clock rates that much with the 65nm process. I believe the FX62 is still on 90nm, and for the moment at least, the 65nm process will be used on the mainstream processors, to get the power requirements down to 65W, and 35W for the low power chips.
sr4470 said:Would we have conroe if AMD hadnt produced K8 to beat down the Netburst P4\Xeon? Its in our interests for AMD to come up with a solution that rivals Conroe (competition, price drops, tech advances etc), although that may not happen for 6-12 months yet.
Yes wait for K10. It has Hyperthreading 2.0. Not 12 months away, more like 16-18 months. It's not on their roadmap anyway.sr4470 said:Would we have conroe if AMD hadnt produced K8 to beat down the Netburst P4\Xeon? Its in our interests for AMD to come up with a solution that rivals Conroe (competition, price drops, tech advances etc), although that may not happen for 6-12 months yet.
NathanE said:Yes wait for K10. It has Hyperthreading 2.0. Not 12 months away, more like 16-18 months. It's not on their roadmap anyway.
Well yeah... you know what I mean.Corasik said:Whatever K10 may or may not have, it wont have a system called Hyperthreading. That design, and name is trademarked and knowing american industries probably has patents applied for.
"Hyperthreading" or symmetric multi-threading (SMT) just refers to any logic that helps the processor keep its pipeline(s) full.Corasik said:If you mean what people call reverse hyperthreading, then someone should think of a better name, as a system to run unthreaded applications on multicpus really shouldnt be called hyperthreading anyway.
Multi-core and multi-threaded software is indeed where future scalability will come from. However neither manufacturer have turned their backs (yet) on single threaded performance. A "reverse Hyperthreading" feature (or what I like to call HT v2.0) is simply a way for a thread of execution to utilise the pipelines of all (or a selection of) available cores on the chip when they would otherwise be idle or free pipeline space is available. Super-duper-scalar chips like the IBM POWER have had this sort of technology for donkey's years.Corasik said:Its also pretty pointless, as both AMD, and Intel have quad core cpus on the roadmaps by then, and the programmers will hopefully be writing multithreaded code anyway.
It'd be nowhere near that. Only certain instructions can be parallelised. I'd say the gains would be closer to 15-25% under optimal conditions.Minstadave said:Reverse hyperthreading would be very interesting, currently nearly everything is single threaded, if you execute that single thread using multiple cores resources that would be very interesting indeed. A dual core processor running a single thread at twice its clock speed would be a beast.
NathanE said:It'd be nowhere near that. Only certain instructions can be parallelised. I'd say the gains would be closer to 15-25% under optimal conditions.
Minstadave said:...most of the time you've got one core sat there doing not very much, may aswell put it to use