
AMD's Roadmap revealed 298
NoPants writes "It looks like the aces at Anandtech were able to get their hands on some of AMD's internal roadmaps. Anand has some interesting information including the new upcoming Socket 939 CPU standard as well as AMD's predicted release dates for Athlon 64 4000+ processors. Hopefully this will shed some light on what AMD is trying to do with all the different socket types..."
Maybe all of this... (Score:5, Funny)
Re:Maybe all of this... (Score:5, Funny)
Re:Maybe all of this... (Score:3, Interesting)
Re:Maybe all of this... (Score:2)
Re:Maybe all of this... (Score:2)
Re:Maybe all of this... (Score:2)
First of all, "P4" isn't a core, it's an architecture. Secondly, please cite your source for this "11GHz" remark. Thirdly, Prescott couldn't possibly ramp that high, so they'd have to go through at least two more generations of cores before even approaching that frequency. And lastly, getting to 11GHz on the P4 architecture would be both incredibly difficult and to an extent, pointless. Somewhere around 10
Re:Maybe all of this... (Score:2)
Re:Maybe all of this... (Score:3, Funny)
Insert some joke about Sexium (at last?) here.
Re:Maybe all of this... (Score:2)
Re:Maybe all of this... (Score:2)
- Exium
- Ettium
- Optium (don't miss this!)
- Ninium
- Decanium (the old processor?)
Re:Maybe all of this... (Score:3, Funny)
well thats nice (Score:5, Insightful)
Re:well thats nice (Score:3, Insightful)
The more they release these fire breathing, heavy Watt using, frying pan of CPU's, the easier it gets on our pocket books.
Wake me when a cheap "build your own system" RISC alternative hits the market.
Re:well thats nice (Score:5, Informative)
Or are wanting to do things like rip MP3s (trivial) or burn DVDs (non-trivial; technically it's the MPEG2 mastering, not the burning, that takes the CPU time). Developers, graphics artists, and most engineering can also use as much CPU as is available. For just a plain old file server you do very well by using the cheapest (in terms of purchase and run cost) that you can get. A webserver probably needs more juice. A database server definitely does. Trivial home use excluded of course. I'm not talking about trivial usages -- they can always be solved easily.
Wake me when a cheap "build your own system" RISC alternative hits the market.
When you realize that the core ISA of all x86 chips is RISC let me know. Not to mention that most of the classic "RISC" designs have deviated far from the "reduced" portion of that moniker. Looked at the Power or PowerPC ISA recently? RISC was created not because a reduced instruction set is inherently better, but because it allowed for a number of technologies such as pipelining, branch prediction, caching, and so forth to be implemented. Every single one of those is in x86 architecture now. Sure, the ISA is still a mess, but it's a better price/performance than anything else out there. All the naysayers have been disproven, time and time again. And yes, when I was a little college student I was horrified at the design of x86. Then I grew up.
Re:well thats nice (Score:3, Interesting)
Right on... Also, most developers need all the juice we can get. Faster compiles, better testing environment (more VMware sessions), etc, etc.
All these people that say "nobody need anything more than X" are idiots. If a 700 Mhz proc works for you then fin
Re:well thats nice (Score:2, Informative)
Disagree. I use a 2.4Ghz at work and a 533Mhz at home and can't really tell a difference, except when (un)zipping files, or installing software(maybe 1% of my total use of the machine). My home machine can play music, games, surf the web, edit docs, etc. just fine.
> Faster boot times, faster archive extracing, faster application start times.
I think the faster dis
Re:well thats nice (Score:3, Funny)
I saw the light, it was the glowing heatsink.
Re:well thats nice (Score:3, Interesting)
AFAIK, x86 units since the i686 have all used a RISC-like core that runs x86 ops by breaking them down into micro-ops and reconstituting them. It -works- but whay do that when the real thing is available?
I think PowerPC would have a real future if MS lost full dominance of the PC market, it's a very short leap from Linux/OS X/BSD/w
Re:well thats nice (Score:2)
Uh, because it works well, is producing results that are better than "the real thing", and happens to run all those existing millions of programs out there without any problems?
I think PowerPC would have a real future if MS lost full dominance of the PC market
Yeah, and Segway might have a real future if it wasn't for all those pesky cars out there. (No, not a perfect analogy, but they're equally based in reality)
This is exactly the kind of
Re:well thats nice (Score:3, Informative)
But the PowerPC line has superior signal processing capabilities these days
According to who? And why? SSE2 provides plenty of instructions for signal processing, and SSE3/PNI will fill in a couple of the last remaining holes. AMD64 also doubles the number of registers for SSE2 as well as the general purpose registers.
Exactly what advantage does the PowerPC have for signal processing? They do have a nifty multiply-add instruction that is missing on x86/SSE2, but on the flip side their vector proce
Re:well thats nice (Score:2)
Unless you want to factor in things like power consumption....
Re:well thats nice (Score:3, Informative)
Feel free to. x86 is still cheaper. Equivalent speed systems don't use vastly less power. Best number I've seen is ~75W, which is 3/4 of what a P4 or Athlon64 uses. That's not an abundance in savings.
To put it clearly -- 25W saves you 219 kWh/year (assuming it's on 24 hours a day year round (365.25 days/year)). If electricity costs $0.10 kWh then that's a savings of $22. Wow.
And that, of course, is assuming that the CPU is fully loaded the en
Re:well thats nice (Score:5, Interesting)
Yes, MOST of what people really need to do can be done on a 500 MHz machine. Shit, most of what people do -- search for information, write email, word process -- can be done on a goddamn Commodore.
It is a fact of life that computers are going to get slowly faster, and people are going to expect these faster computers to have better software. Even if it's mostly superficial, we try to deliver that. Most of the time, though, a faster processor is a boon even to Joe Q. Homeuser. Consider a 3 megapixel camera, delivering photographs in excess of 1.5 megabytes. Time was we'd never THINK of doing graphical operations on that much information. Nowadays, it's so trivial that many photoalbums are processing 10 or more such pictures per second!
Anyway, for easy operations like file serving, running a firewall, serving 100,000 or fewer web pages per day, etc...your best bet is a processor with a fast bus and a slow clockspeed. It'll be cooler and more reliable than some 64 bit god (honestly, who needs 64 bits to send packets?)
Re:well thats nice (Score:2)
While I agree that with a well-designed computer, 500MHz is very good for most people, I would bet that most of the 64 bit RISC systems are more reliable than most of the x86 systems, although I can't say much about Athlon 64 / Opteron, it hasn't been around for long enough. My daily-use Alpha built in 1997 ran Windows NT 4.0 to an uptime of 104 days. After that I quit just because it was a waste of power, although certainly more efficient than most
Re:well thats nice (Score:2)
OTOH, my firewall is a PentiumMMX/200 and it does just fine, thankyouverymuch.
Re:well thats nice (Score:2, Funny)
Re:well thats nice (Score:2)
Re:well thats nice (Score:2)
Hey, a C64 could finish that task as fast as the earth simulator!
*hint* In case you didn't know, Pi has an infinite number of digits. Scary, huh?
Re:well thats nice (Score:2)
Re:well thats nice (Score:2)
I fear you may never awake from your slumber.
Re:well thats nice (Score:2)
If it could do it four times faster at the max HDD throughput (40MB/sec) it'll be done in 17 minutes.
In this case the bottleneck is the CPU or perhaps the software - anyone know of a faster gzip?
HOWEVER, if a CPU is 4 times faster so as not to be a bottleneck for the HDD gzip, the HDD then quickly becomes a bottleneck for other scenarios
Re:well thats nice (Score:2)
The built-in zip is handy, but it killed the explorer when I tried to use it, moments after first install, and that didn't make a good impression.
Re:well thats nice (Score:4, Funny)
Your mind will change quickly.
Re:well thats nice (Score:2)
I will guess not. My 1.4 Ghz TBird C may have the speed I need but there are new features I would like which is why the A64 is getting such a big push from me personally as my upgrade option. Plus it will hit the magic sub 150$ mark before the Prescott hand warmer.
Re:well thats nice (Score:2)
What's your point? That we should stop making faster CPU's? Why do you care?
Here's the post I want to see:
Well that's nice, but my 286 that runs Minix is great! you don't really need that 700mhz proc, it's a total waste.
Re:well thats nice (Score:2)
Re:well thats nice (Score:2)
100Mhz? Who needs it? My 486/66 can run Vi, gcc, and one or two other apps. What else do I need?
Still not convinced (Score:4, Insightful)
*Do they really need to be different products? Opteron is your product for server/high-end workstations, Duron (and now Athlon XP) is low-end... you want Athlon64 to be mainstream, right?
*Is it really a good idea to have the memory controller on the CPU? OK, I buy that it increases performance, but it hasn't lowered mainboard costs and all I've seen it doing is causing a rift between the A64 and AFX product lines, since Athlon64 doesn't have a dual-channel memory controller.
*Why in the world introduce an AthlonFX based on Socket 940, especially at the outrageous price, when you're moving to socket 939 imminently?
I think it would have been more of a slam-dunk as a platform and a "brand" to release Athlon64 as all dual-channel, all Socket 939 (or some standard), and left Opteron as the high-end platform. Any other takers?
Re:Still not convinced (Score:3, Informative)
Simple really. AMD feared that Intel was about to release the next revision of the P4 aka. Prescott. The 940-pin FX was an attempt to get something out the door ASAP.
Unfortunately that means that some people might be caught at a loose end when it comes to upgrade time, but that is not clear cut at this stage to my knowledge.
Re:Still not convinced (Score:2)
On the other hand, your question about having the memory processor directly on the processor. It is the best idea ever, and you may not understand this, being a desktop user, but being in IT when I was young, and now in the money end of IS, I understand the value of the system amd is i
Re:Still not convinced (Score:3, Interesting)
Re:Still not convinced (Score:2)
Re:Still not convinced (Score:2)
Re:Still not convinced (Score:2)
Same reason Intel released the PIV EE (Score:2)
Because AMD were making Opterons. And then some bright head said "Why not rebrand the 1x Opteron to AMD FX and sell it as the worlds fastest desktop system, 64 bit desktop, and whatever else? That way we can ship it NOW."
And Intel's Emergency Edition was almost the same thing. Basicly a rebranded Xeon, if I understood it right. Lots of cache, also hideously expensiv
Re:Still not convinced (Score:5, Informative)
The marketing of the Athlon64 FX has become a bit confusing. It kind of made sense for the initial launch to combat a precieved weakness of the design compared to Intel's P4 though. With the P4 you get up to 6.4GB/s of memory bandwidth, while the first Athlon64 would only have 3.2GB/s of memory bandwidth. Now, it turns out that the extra bandwidth doesn't actually buy you much on most applications, but this was seen as a weakness, hence the Athlon64 FX. With Intel bringing out the P4EE to compete with the FX, now AMD might need to keep the chip, even if it isn't a worthwhile product (The P4EE isn't a worthwhile product either).
*Is it really a good idea to have the memory controller on the CPU?
Yes, yes it is a good idea. A VERY good idea in fact. Memory latency has only improved by about one order of magnitude in the past 15 years. Meanwhile everything else in the system has gone up by at least two orders of magnitude. Virtually everything that is being done in CPU design these days is to hide memory latency (larger caches, out-of-order executation, branch prediction, even SMT).Integrating the memory controller reduces latency by 20-30%. At 2.0GHz this makes a BIG difference (this is the main reason why a 2.0GHz Athlon64 is faster than a 2.2GHz AthlonXP), at 4 or 5GHz the difference will be huge.
but it hasn't lowered mainboard costs
You can buy new Athlon64 motherboards for only $100, only 3 months after the chips release. It took ages for Athlon or P4 motherboards to reach that price point. What's perhaps even more impressive is the dual-processor boards that are only $200. In short, it HAS reduced motherboard costs, whether you've noticed or not. It also means that ALL Athlon64's support ECC, chipkill and a few other nifty reliability features, regardless of how badly VIA screws up their chipset design.
*Why in the world introduce an AthlonFX based on Socket 940, especially at the outrageous price, when you're moving to socket 939 imminently?
The Athlon64 FX was a bit of a last minute decision I believe. They found a marketing weakness and wanted the quickest and easiest solution they could find. The answer? Sell your server chip as an "enthusiast" chip. Intel did exactly the same thing for the same reason with the P4EE.
Also, it's actually VERY normal to switch sockets soon after releasing a new processor. Intel's upcoming Prescott will use Socket 478 for only about 6 months before switching to socket 775. The original P4 used Socket 423 for a very short time before switching to socket 478. The original Athlon used Slot A for a year or so before switching to Socket A. The PIII came out in Slot 1 form but then switched to Socket 370 about a year later. The Celeron followed the same path a couple years before.
I think it would have been more of a slam-dunk as a platform and a "brand" to release Athlon64 as all dual-channel, all Socket 939 (or some standard), and left Opteron as the high-end platform. Any other takers?
In retrospec that might seem like a good idea, hindsight is 20-20 after all. However the original split of ALL Athlon64 chips being socket 754 and ALL Opteron's being socket 940 seemed to make the most sense when AMD was desigining them. It wasn't until market conditions changed and a new perceived weakness was discovered that AMD felt they need a consumer chip with a 128-bit wide memory bus. By that time the chip was already late to market and designing a new socket would have added more delay to the equation.
There's also the question of budget chips. AMD hopes to move their entire product line to the Athlon64/Opteron platform by the end of 2004. That means they need a budget chip, and socket 939 with it's 128-bit wide memory bus is problematic for that. Hence the continued existance of Socket 754 and the AthlonXP for that platform.
Re:Still not convinced (Score:3, Informative)
Actually, read the roadmap. AthlonFX and Athlon64 will both be Socket939 and dual-channel memory controller products by the end of 2004. The chips will be the same, except A64 will have 512k cache and AFX will have a full meg.
This actually makes a lot of sense, and should have been the way it was done from the start. No socket 754, no socket 940 (except Opterons), just a "mainstream" and a "performance" product.
Global Warming (Score:4, Funny)
Seriously tho. I think AMD ought to work some better thermal performance into its cpu range. A low cost, low temperature, high performance CPU is what is required in the market.
Intel is the Global Warming threat (Score:5, Informative)
AMD CPU power requirements are expected to drop substantially when they switch to 90nm in the second half of this year. OTOH, Intel's prototype 90nm Tejas CPU burns up 150 watts
AMD chips haven't used more electricity than Intel chips for years. Pay attention.
BTW, Athlon 64 notebooks are out [bestbuy.com]. $1,550 for a widescreen 64-bit notebook! I'm going to stick with my Athlon 64 desktop, at least until I come up with an excuse to buy a portable. Really, I am...
Re:Global Warming (Score:5, Interesting)
The P4 generates more heat than the Athlon (any variant) for the same performance.
It is such an old, and incorrect joke it isn't even funny anymore.
Socket, shmocket ... I want RAM! (Score:5, Insightful)
Re:Socket, shmocket ... I want RAM! (Score:5, Funny)
Re:Socket, shmocket ... I want RAM! (Score:2)
After all, only the fotune 500 buy "servers", they can afford it
Bullshit. (Score:2)
Unless you meant to be funny. But really, they're not THAT expensive. Look to spend about $600-$1000 on a board that can support 8+ GB ram.
Re:Socket, shmocket ... I want RAM! (Score:2)
Re:Socket, shmocket ... I want RAM! (Score:4, Informative)
Here. [ewiz.com]
Re:Socket, shmocket ... I want RAM! (Score:2)
Re:Socket, shmocket ... I want RAM! (Score:2)
Re:Socket, shmocket ... I want RAM! (Score:2)
I think the Tyan K8W Thunder may be your best bet, but I'm not sure it can do 32GB. It is Opteron-only. If you need it that sort of power, it is well worth it.
Re:Socket, shmocket ... I want RAM! (Score:2)
socket types (Score:5, Funny)
Making us buy more motherboards, of course!
Dual Processors? (Score:5, Interesting)
Re:Dual Processors? (Score:2)
Not that it matters to me, I just stick ECC into everything I can, it really isn't that much more expensive. While it might slow performance a tad, ECC becomes even more necessary if you need to use multiple gigabytes of RAM.
Re:Dual Processors? (Score:2)
G5 looks like ramping up faster (Score:5, Interesting)
Re:G5 looks like ramping up faster (Score:5, Interesting)
Top 5 things you will do with your Athlon64... (Score:5, Funny)
Compute Pi to 5.497558e+11 bit precision during your lunchbreak.
Store this value of Pi in RAM.
Install Kazaa and not notice the spyware slowdown.
Use the faster page loading times to get FP more often.
Re:Top 5 things you will do with your Athlon64... (Score:2)
I would not want to run doom3 on my athlonXP 1700 with a limited geforce4TI. That is for usre.
Re:Top 5 things you will do with your Athlon64... (Score:2, Insightful)
I seem to remeber the leaked demo running playably on a 1Gig celery and geforce2 MX.
You'd think they've had plenty of time to optimize code since then.
Socket hell (Score:5, Insightful)
939 encompasses both Athlon64/FX chips, starting in Q2.
754 is relegated to the next gen AthlonXPs (with the on die memory controller, but only 32 bit)
462 dies a slow death.
Why can't every CPU made just fit on Socket 7...
Re:Socket hell (Score:2)
socket 754 is single channel memory.
socket 939 (won't fit opteron) with dual channel
ram. 1m cashe = FX, 1m is athlon 64.
Will socket 939 chips work in socket 940 mb?
current athlon64fx chips will work in opteron mbs.
Re:Socket hell (Score:2)
Re:Socket hell (Score:3, Interesting)
Yes.
Like you said some pins are used for memory bus bandwidth and power. Build a generic configuration that supports enough power and bus pins for all your average 256-bit wide buses. So each generic socket would have like 1000 pins. Enough to have direct CPU-CPU, CPU-Memory, and CPU-IO buses and power.
I don't design hardware, but if I did I wouldn't waste so much time redesigning it every year.
Re:Socket hell (Score:3, Interesting)
If we kept socket 7 we would: a.) still be stuck at ~1GHz processors because the socket did not provide enough power or grounding pins for todays faster processors. b.) would have TERRIBLE memory throughput, the real-world performance of this socket was terrible even if when the theoretical numbers were ok.
Perhaps most importantly though, it wouldn't help anything. You would STILL need to buy new motherboards to support new chips. In fact
AMD shot self in foot (Score:3, Insightful)
Re:AMD shot self in foot (Score:3, Insightful)
This means the scale is LINEAR unlike measuring against Pentium speed which is inverse-square (or similar, only done rough calcs) related to performance. You have more certainty with the AMD rating system.
Athlon Thunderbird (Score:5, Informative)
Re:AMD shot self in foot (Score:2)
Umm... yes you can. Most Joe Sixpacks can extrapolate the performance.
Dual CPU capability? (Score:2)
confuse much? (Score:3, Insightful)
They've got to the point with all these different lines that it's no longer possible to talk AMD CPU's with anyone but the most avid AMD enthusiast. If you do try to talk the talk it ends up being a group memory excercise to see if together we can remember 50% of the difference in the varying jungle lines of processors.
Opteron is a good thing. Keep it simple. Give the FX a real name too. Don't call it an Opteron FX or 64 FX or whatever the hell it might be. Give it a damned name. How about an AMD Jargon? That would be a good name for a processor. If they all had names, you could associate the capabilities of the lines to the names and people could pick a favorite and learn the product.
As it is there must be extremely few people that can rattle off all the cache sizes, 398043+++ ratings, what core it is, blah blah blah. Not only do the different lines have different specs, but there are different specs within a line. There several instances of the same + rating with different specs in the same line. "I got a 2600+" "Which one?"
Not that I won't do all the research before I buy the next one, but I envy the Intel enthusiast that can just look and say Bigger is Better, and buy what they can afford.
I can't imagine my the other members of my family buying an AMD. They'd have to take a 3 week course, 2 hours a day, before they'd know which of the AMD's to buy. "This one costs more, but is it better?" "I have no idea." "This one has a bigger rating." "Yeah, but I heard this one is more advanced."
Is AMD hoping nobody will know what they're buying? Is that the ultimate goal? Why not just put a random number on each chip and put a MSRP on it and call it good.
Re:confuse much? (Score:5, Insightful)
The idea is that you don't have to know what the exact specs are. What AMD is trying to do is show that CPU performance is relative. Within a few percentage points, every 2600+ CPU will perform equally, regardless of its core, amount of cache, socket, memory lines, clock frequency, etc. That's the whole point - you don't have to know. If you're "in the know", you can look at individual 2600+ CPUs to see which one has more of what will help you in the specific applications you use. If you're a general user, then 2600+ is the only thing you need to know. How many people buy a 3.06GHz P4 instead of a 3.00GHz P4 because they think the former is faster? The clock frequency alone belies the fact that the higher FSB on the latter CPU will actually make it perform far better on nearly every application. AMD is trying to hand you the whole package in a single number to simply the buying process for everyday people.
The fact is, neither AMD nor Intel are telling the whole performance truth, nor could they do so. The only way to do that is to educate consumers about CPU mechanics, latency, IPC, L1/L2 cache, cache hits and misses, branch prediction, pipeline stages, and so on. The average consumer (hell, the average geek) can't understand half of these things. Thus, Intel has chosen to show the clock frequency of its CPUs, and AMD has chosen to use performance ratings that give consumers a performance index relative to the Athlon's Thunderbird core. Neither system is perfect, but neither system is more imperfect than the other, in my opinion.
"Is AMD hoping nobody will know what they're buying?"
AMD is hoping that those who need to know, will know, and that the rest who buy the "bigger number" will at least have an idea of what to get.
What is the FX's market? (Score:3, Insightful)
The plain Athlon 64, sure. I see why someone would buy that. If you want decent performance but also want to keep things dirt cheap, that's a nice chip. I think a low-power "mobile" version of that processor will also be a winner.
But if you want to spend a little extra money and build a "hotrod" machine, the Athlon 64 FX is a dumb move. Most CPU-bound stuff that people do, is parallelizable. (The only major exception I can think of, is that today's apps for multimedia encoding, tend to not take advantage. But they could (e.g. the portion after every key-frame could be handled by a different thread).)
So just spend a little more (it's really not much) and get multiple Opterons. If you're really hurting for money, get "obsolete" 240 models, and two of them will still run rings around any Athlon64FX or single-P4EE system that money can buy.
The class of problems that can't take advantage of multiple CPUs but still needs lots of speed, is small. Maybe I'm just being dumb, but I just don't see a market for a socket-939 or single-socket-940 board. Why would AMD, and motherboard manufacturers, bother to spend money development something that hardly anyone needs?
Athlon 64: Boon for Unix/Linux/BSD (Score:3, Interesting)
And since Microsoft is once again behind the curve, the various freeware Unix platforms could benefit a great deal by trumpeting their inherent advantage over Windows in these key areas.
Re:offtopic.. (Score:5, Funny)
Re:Grhh... (Score:3, Interesting)
Re:Grhh... (Score:3, Informative)
I agree it's all marketing, but
As a data-point, I recently upgraded from an Athlon 2400 to the 3200 -- a 30% improvement in "PR," and saw my benchmarks go up almost exactly 30%. By benchmarks here I'm talking about a CPU bound computational mechanics code I wrote for my thesis. About as useful to everyone else as SPEC, but very relevant to me.
As usual, YMMV.
Re:Grhh... (Score:5, Interesting)
What's the problem. They're saying that having the smaller cache gives you less performance. Are you upset that they happen to have the same clock speed? I assume you'd prefer nomenclature more on the order of "AMD Athlon 64 2.4/512 and 2.4/1024"? In many ways they way they are currently doing it is more descriptive to the average buyer. No guessing as to how much performance you're giving up by going with the smaller cache
Re:Grhh... (Score:5, Insightful)
Re:Grhh... (Score:2)
The lower clocked, bigger cache part does run a bit cooler though, so if
Re:Grhh... (Score:2)
Re:Grhh... (Score:2)
The rest of us who cared about the details (which software, how fast) can and would find them out fairly easily.
Re:Grhh... (Score:4, Insightful)
Also, normal users don't care about 10% performance differences. I've found a good way to relate to this is to think about old computers. Do you really think of the difference between a P133 and a P166? No, they're both from the p5 generation, with a L2 caching up to 64MB or 128MB depending on chipset and the cpu performance is basically equal (slow). If a p166 will do the job you need nowdays, a p133 probably will too, and it's doubtful that you'll notice much difference.
Re:Real Mhz on the 4000 chip? (Score:5, Insightful)
Re:Real Mhz on the 4000 chip? (Score:2)
Anyone waving Tom's Hardware in your face is part of the "Knows Just Enough to be Dangerous" crowd anyway. These are the folks who think that reading a dumbed-down article or review makes them knowledgable enough to render a viable opinion.
They're also the people who burn up their mainboard and CPU trying some voltage mod they read about, then want to return everything for a refund because it no longer works.
Re:Does it really matter? (Score:2, Insightful)
Also, the Athalon64 and AthalonFX chips blow the old XP chips out of the water, so it's not equivalent at all.
Re:Does it really matter? (Score:2)
I believe, IHBT.
There ARE 64 bit OSes (Score:2, Informative)
If you need better performance it may be another reason to switch to linux
Only Microsoft didn't catch up, but who cares ;-)
Regards
Re:I used to be a AMD fan (Score:3, Insightful)
Re:I used to be a AMD fan (Score:3, Insightful)
Intel decided to market their processors using one totally meaningless measure of performance, the clock speed.
AMD decided to market their processors using a different totally meaningless measure of performance, the model numbers.
The problem with the chips is not so much sleezy marketing as with are ridiculous focus on clock speed. That's like buying a car
Re:Like a Cartoon Roadmap? (Score:2)