|This is the talk page for discussing improvements to the Athlon 64 article.
This is not a forum for general discussion of the article's subject.
|WikiProject Computing||(Rated C-class, Mid-importance)|
- 1 Untitled
- 2 What is with the weird redirect for Athlon 64 FX?
- 3 Some changes
- 4 Differences and distinctions, please
- 5 Merging Athlon 64 FX and Athlon 64 pages?
- 6 Confusing memory terminology
- 7 It should be merged
- 8 Should there be a page for the K8 microarchitecture?
- 9 Athlon 64 FX-60 released!
- 10 Requested move
- 11 Further comments on moving
- 12 K8's sucessor, K8L
- 13 Manchester core / single core
- 14 About the DRAM speed formula
- 15 Main 939 benefit
- 16 List of models
- 17 "Hardware-set permission levels"
- 18 Mobile Athlon 64
- 19 Which is which?
- 20 Added "update" tag, some suggestions
- 21 What is the orignal AMD K8?
- 22 Athlon 64 - consumer-oriented?
- 23 Bear, not bare
- 24 External links modified
It's a alot better that the x2 has it's own page since the tech is different and people who are looking for information actually get a good digested form of what the x2 is all about. JPN --184.108.40.206 23:29, 9 August 2005 (UTC)
What is with the weird redirect for Athlon 64 FX?
Click on Athlon 64 FX. I don't think it should be redirected to the basic article about the AMD Athlon. If you guys are re-directing that term, I think it should point directly to this article. Just my opinion. --Anonymous Cow 20:35, 15 Feb 2005 (UTC)
- I've checked, it appears that it was a article before for about a year and it was redirected recently (Feb 14). I reverted the redirect. The Athlon 64 FX should have a seperate article because of the differences between the two proccessor types despite the similar names. Norman Rogers\talk 23:03, 15 Feb 2005 (UTC)
Any chance it could get changed from "it competes with the pentium 4" to "it competed with" P4 are out of production and they now compete with Core based CPUs.
I have made some changes.
For an article to have a subheading "Athlon 64" even though the article has a title "Athlon 64" seems a bit redundant.
I removed references to the Athlon 64 architecture (Athlon 64 is a product that implements the AMD64 architecture. There is no Athlon 64 architecture), and information abou the AMD64 architecture that is not specific to the Athlon 64 processor. This fits the pattern of the rest of wikipedia, where articles about processor products don't go into details about the processor's architecture, but instead just point out that they implement a certain architecture, and let the AMD64 article handle that information.
Samrolken 01:42, 18 Sep 2004 (UTC)
Differences and distinctions, please
Can someone differentiate between "ClawHammer", "Newcastle" and "Winchester"? Thanks.
DanielVonEhren 23:22, 20 Feb 2005 (UTC)
- The article should say something about the different revisions of the Athlon 64. Clawhammer and Newcastle are basically the same processor, but with only 512 kB Cache in the latter case. Both can either be revision C0 or CG. CG has an improved memory controller and is more energy efficient. Then came revision D0 aka "Winchester" (90 nm with an even more improved memory controller and less power consumption). --Echoray 17:03, 21 Feb 2005 (UTC)
Any chance the person who "should say something" could be you? :-)
DanielVonEhren 19:35, 21 Feb 2005 (UTC)
Merging Athlon 64 FX and Athlon 64 pages?
It seems that Athlon 64 page contains info also about FX model, and in the future maybe X2 dual cores also. Currently there is at least short article about FX cores, so should those be merged? --Thv 10:18, 2005 May 4 (UTC)
- Both the FX and the X2 should have their own article - they are different than the standard Ahlon 64. --Denniss 12:26, 2005 May 4 (UTC)
- A question: how is it that the Athlon 64 FX gets its own page when ALL K7-based Athlons (from Pluto to Barton) share the same page? The modern Socket 939 Athlon 64 FX is pretty much just a San Diego with unlocked multipliers, but there are many differences between the Athlon Classic and Athlon XP. SVI 22:47, 26 July 2005 (UTC)
- I've now added merge request from Athlon 64 FX and Athlon 64 X2. Currently this page contains some info about X2 and FX, and also List of AMD Athlon 64 microprocessors contains also FX and X2 models. Thv 07:18, July 27, 2005 (UTC)
- PS. List of AMD microprocessors separates X2 from other Athlon 64 models as K9 series, thus at least FX should be merged, but maybe X2 can have it's own article? Thv 07:22, July 27, 2005 (UTC)
- X2 should definately not be merged, FX could be however, as it is exactly the same as the normal A64, just the higher end model. Bluemoose 08:35, 27 July 2005 (UTC)
- How do we merge the rival Intel processor(s)? We separate the desktop from the server processor, but do not separate the performance advanced version from the normal consumer version (nor the dual core). I'm an AMD guy atw, but whatever we do to Intel we need to do it to AMD... unless there is a big difference or special situation. Is the X2 a special situation? Dual core is new but nothing special. FX is a high end consumer edition, but eh... Overall I'd like Athlon 64 and Pentium 4 go one way or the other, and that means I want Athlon 64 combined and merged. --x1987x 17:12, July 29, 2005 (UTC)
- X2 is just two A64 cores on one die. They are different processors, but I am unsure as to whether they are different enough to justify separation. Besides, article separation is not done on a technological basis; Pentium II and Pentium III are separate articles, even though early (Katmai) P3s are the exact same as late (Deschutes) P2s with just SSE and the infamous PSN added. More significantly, the Celeron article includes Celerons from Covington to Dothan to Prescott; there are HUGE technological differences between them all. Processor articles are separate on a name basis, not a technological basis-- and even if they were on a tech basis, surely two of the same core is a smaller difference than a complete arch shift (as with, say, Cu128 Celerons and Willamette Celerons). For these reasons, X2 should definitely be merged.
- Also, List of AMD microprocessors is wrong, and has since been corrected. AMD themselves classify the X2 processors as K8, as does sandpile. K9 was originally meant to be dual-core, but AMD revised their plans. K9 is cancelled, or at the very least not in official existence yet.
- The 64 FX is easy. It's almost identical to a regular 64 AND is also an "Athlon 64". Definitely merge. SVI 01:12, 30 July 2005 (UTC)
- X2 should definately not be merged, FX could be however, as it is exactly the same as the normal A64, just the higher end model. Bluemoose 08:35, 27 July 2005 (UTC)
I vote for merging both articles into this one. The FX should be merged without a doubt. As for the X2, AMD renamed their K9s to dual core K8s a LONG time ago. Each core in an X2 is really just a regular K8, so a merge is definitely in order. Somebody just do it already.the1physicist 02:32, 30 July 2005 (UTC)
- An athlon x2 is not "just" 2 cores on one die (well, ok it nearly is) intels dual core is just 2 cores on one die, However as long as no info is lost and it is still clear I won't cry if they are merged. Bluemoose 22:31, 31 July 2005 (UTC)
- And a Venice isn't "just" a Winchester with SSE3, but the other differences are so minor that they barely deserve mention. Same applies here. Besides, as I said, it's done by nomenclature, not technological advances, so even a huge difference among processors with the same name would not merit article splittage. SVI 23:05, 31 July 2005 (UTC)
Well, if no one else is going to do it, I'll merge, scared newbie or no. All relevant info on the A64FX except the SH core (130nm Opterons, used for the early 940 FXes) was already in this article, so I just copied over SledgeHammer and redirected Athlon 64 FX to this article. Are there any objections to merging Athlon 64 X2 with this article? SVI 18:06, 8 August 2005 (UTC)
- Please update the Athlon 64 article with all Athlon64 FX info found in the old article !! And do update the cores with the FX model numbers as well. Do not merge the Athlon64 X2 - if ou are doing this then please don't forget to merge the Pentium D and EE into the Pentium 4 as well !! The X2 is more then just using two dies on one core as Intel tried on these two CPU. --Denniss 22:24, August 8, 2005 (UTC)
- Already did, the 64FX is practically identical. And as I've said before, articles are not separated on a technical basis, they are separated on NOMENCLATURE. The "Pentium D" is not the Pentium 4D (that's Gallatin, if sandpile is to be trusted), it is a "Pentium D"-- its different name merits a different article. (The same goes for the "Pentium Extreme Edition", although not the "Pentium 4 Extreme Edition".) The Athlon 64 X2, on the other hand, is clearly an Athlon 64 variant. The Celeron article includes processors from Covington to Northwood, surely a much bigger difference than just two cores (and yes, that's pretty much what it is-- I realize that AMD has a special interconnect, but that doesn't make the tech gap any larger). The Pentium III article includes IIIE, IIIEB, and late Tualatin variants, because they're ALL PENTIUM IIIs. Are there any objections that I haven't addressed? SVI 06:27, 9 August 2005 (UTC)
I again vote to merge the X2 article. There is no reason to keep them separate. Whoever did the FX merge, good job.the1physicist 01:25, 10 August 2005 (UTC)
Merge of Athlon 64 X2 to Athlon 64
There have been many objections against this merge, and I understand that X2 can have enough content to deserve own article. However, my main point is that currently intro chapter of Athlon 64 says that X2 is one of three variants of Athlon 64. So if the intro chapter contains clear difference between X2 and other processors called "Athlon 64 anything", then I won't object removing merge request. --Thv 07:49, August 10, 2005 (UTC)
Confusing memory terminology
"940: Opteron and old Athlon 64 FX, 128-bit memory interface - Requires registered DDR memory, but can use ECC"
- This wording is misleading, and possibly inaccurate: Registered DDR and ECC are far from mutually exclusive--they are usually paired—Trevor Caira 12:52, 9 August 2005 (UTC)
- You're right, that's very misleading. Removed the ECC bit, as it was kind of pointless anyway. SVI 15:33, 9 August 2005 (UTC)
It should be merged
The Athlon 64 X2 bears very little difference from its single core brethren, other than a second core being linked through the integrated crossbar. At its heart, an Athlon 64 X2 is in reality two Venice or San Diego cores fabricated next to each other and linked by that crossbar. As a result, the data of this page should be merged with the main Athlon 64 page, which currently lacks a lot of information about the X2 processor.
- I think they should not be merged as 1) Athlon 64 will become too long and complicated; 2) if a person searched for "athlon x2" they would be disappointed to be redirected to the athlon64 article; 3) the athlon x2 article is clearly long enough to sustain itself, it's hardly a stub, and it duplicates very little material. Martin - The non-blue non-moose 18:51, 16 August 2005 (UTC)
- Athlon 64 is not nearly as long or complicated as other articles; I doubt anyone would be disappointed to find a redirect to the relevant article; this has nothing to do with duplication. Again, I point to the Celery article as an example: it's long, there are no separate articles for the (significant) core differences, and even if you split all the cores into separate articles there'd be no duplication.
- The issue here is that the Athlon 64 article should list all the Athlon 64s. The Celeron article lists all the Celerons regardless of differences and length, Pentium 4 has everything from the original suffix-less Willamettes to the A/B/C Northies and A/E Prescotts, Pentium MMX redirects to Pentium. It's, again, a question of nomenclature. SVI 10:27, 18 August 2005 (UTC)
- The FX may be a variation but the X2 is a little bit different from every single core Athlon 64. --Denniss 12:20, August 23, 2005 (UTC)
Should there be a page for the K8 microarchitecture?
Are the micro-architectures of Opteron, Athlon 64, Turion 64, etc. sufficiently similar that there should be an "AMD K8" page for the K8 micro-architecture, with the pages for particular K8-micro-architecture chips referring to it (as is already done for Intel P6, NetBurst, and Intel Next Generation Microarchitecture)? (If so, an AMD K7 page might also make sense.) Guy Harris 01:24, 9 January 2006 (UTC)
- I've wondered about that (more in the context of the lack of a K7 article, but K8 too). I do think such a thing would make sense; processor articles seem to be devoted mainly to describing the history and forms of said processor rather than in-depth technical details, and most people looking for technical details would probably look up the architecture rather than the brand name of one of the processors based on said architecture. Plus, as you said, there's quite a precedent with P6 et al.
- In short: I think it makes perfect sense, and I'd support such a thing, but I am too lazy and uneducated to make something like that myself. SVI 05:35, 9 January 2006 (UTC)
- Yes, there should be a K8 page, and it would be that of the Opteron, Athlong 64, X2, ... 220.127.116.11 21:56, 23 January 2006 (UTC)
- And now we see why a "demerge" template was suggested on Template_talk:Split; the "split" template speaks of a disambiguation page, but none would be needed here. As there isn't a "demerge" template, "split" will have to do. Guy Harris 22:48, 23 January 2006 (UTC)
Athlon 64 FX-60 released!
As it was, the article referred to the Athlon 64 FX-60 as an unreleased CPU. I changed this to reflect its recent release date (today!) and placed emphasis on the dual-core nature of this CPU as opposed to the other models in the FX line. I also defined the analogy between it and the Athlon 64 FX-53, both of which saw/will see two versions for two different sockets (940 then 939 for FX-53 and 939 then AM2 for FX-60). Oh and it's fine and dandy that the Athlon 64 FX and Athlon 64 articles are merged now, but I think the FX series should at LEAST get its own section! Another user pointed out that modern FXes are just Socket 939 San Diego chips with a high clock rate... but let's not forget the architectural basis of the FX line! The Athlon 64 FX-51 was very similar to the Opteron when they both were released originally (even note they were both on Socket 940). Because this gives it a clear distinction between it and the Athlon 64 line, and now the fact that the FX line has both single and dual core items, I think it is worthy of its own section in this article. What do you think? pinky 06:38, 11 January 2006 (UTC)
Further comments on moving
- Oppose - I don't think that this is necessary. Athlon 64 is not less or more specific than AMD Athlon 64. I will agree that if such a change is made, then more products should be changed too (e.g. Pentium 4 as Hahnchen stated). --kostas213 17:07, 26 January 2006 (UTC)
- Oppose - "article naming should give priority to what the majority of English speakers would most easily recognize, with a reasonable minimum of ambiguity, while at the same time making linking to those articles easy and second nature." (from WP:NAME). The usual reference to these processors would simply be "Athlon 64", not "AMD Athlon 64", there is no ambiguity in that name, and certainly it makes more easier and more likely linking. --Stormie 13:23, 30 January 2006 (UTC)
K8's sucessor, K8L
I just created a page for the K8L, would it be good to mention it? Pueywei 14:03, 31 March 2006 (UTC)
Manchester core / single core
There should be a statement under the vencie cores, that some are infact manchesters with a cut HTT bridge between the cores. These prossessors did not make the grade as a X2 but make great single cores. —The preceding unsigned comment was added by Jthull (talk • contribs) .
- Thank you for your suggestion regarding Athlon 64! When you feel an article needs improvement, please feel free to make whatever changes you feel are needed. Wikipedia is a wiki, so anyone can edit any article by simply following the Edit this page link at the top. You don't even need to log in! (Although there are some reasons why you might like to…) The Wikipedia community encourages you to be bold. Don't worry too much about making honest mistakes—they're likely to be found and corrected quickly. If you're not sure how editing works, check out how to edit a page, or use the sandbox to try out your editing skills. New contributors are always welcome. —BorgHunter
ubx(talk) 23:57, 19 May 2006 (UTC)
About the DRAM speed formula
The mathematical expression for calculating the DRAM speed, displayed on the main page is wrong!
The inaccuracy is in the celling function where the "DRAM divider" and "CPU multiplier" parameters must be multiplied NOT divided.
A typical situation to illustrate:
- CPU speed: 2500MHz;
- CPU multiplier: x9;
- DRAM divider: for DDR333 mode == 6/5 ratio;
1. Wrong formula -
(CPU_speed)/(Multiplier/Divider) = 2500/(9/(6/5)) = 2500/(9/1.2) = = 2500/8 = 312MHz for the DRAM interface;
2. Correct formula -
(CPU_speed)/(Multiplier*Divider) = 2500/(9*6/5) = 2500/(9*1.2) = = 2500/11 = 227MHz for the DRAM interface;
- First, there's no A64 with 2500 MHz, either 2400 or 2600 MHz. Multiplier at 2400 MHz is 12 (12x200). I'm not that expert in A64 DRAM interface but I know PC-2700 (using DDR-333 chips, 166 MHz) will run slightly underclocked with standard 200 MHz system clock. Memory divider is CPU frequency divided by memory frequency and rounded up to the next multiplier. Example with PC-2700: 2400/166 = 14.457 = 15. 2400/15 = 160 MHz memory clock. --Denniss 18:53, 4 July 2006 (UTC)
There is 2500MHz or any other frequency in the feasible clock range for the given CPU architecture. Haven't you heard about overclocking? The example above was just a random picked number for the core speed. Whatever, your case is indicative that the DRAM divider can't take halfs but only integer values, that's why memory clock got a little bias because of the divider value rounded up from actual 14.4 to 15. Well it could be in the opposite direction, rouded down to 14, but this will result in non-standart and slightly overclocked memory (~171MHz in this case)... well not that 160MHz is stantard, but it's safer. Fellix 11:39, 10 July 2006 (UTC)
- The formula is fine, you're just interpreting DDR333 as 6/5, when its actually 5/6. 6/5 is 1.2, and using that would be meant to INCREASE the RAM speed, not decrease it; yet DDR333 is meant to produce lower speeds than the normal DDR400. With that in mind, divide works.
DRAM clock = CPU clock / ( ceil(CPU multiplier / DRAM divider) ) = 2500 / ( ceil(9 / (5/6) ) ) = = 2500 / ceil(10.8) = 2500/11 = 227.
- Using a multiplier worked in that case, but switching it back around and using divide produces the same result. To fully prove it to you, take this example:
Multiplier =10.5, LDT = 266, Divider = DDR333 (5/6). 2793 / ceil( 10.5 / (5/6) ) = 215.
2793 / ceil( 10.5 / (5/6) ) = 215.
- With half multipliers, your version of the formula doesnt stand up. If you have an A64 PC handy, give it a try.
- On a final note, please mark your comments with ~~~~. That will put your name etc after your message. AthlonBoy 20:43, 6 July 2006 (UTC)
- Well you'r right for the DDR ratio flipping, but that's simple mathematics - when you divide by fraction number that or either way you have to change the positions of the numerator and denominator and thus "my" formulation comes in to place, so both cases are correct by my mean. Now I wonder how is the case with the new AM2 DDR2 platform? And yes, I have a K8 setup and thus I've verified much enough cases in practice ;). Fellix 11:57, 10 July 2006 (UTC)
- Yeah, AM2 calculates its DRAM speed in the same way. Thats why the speed ends up being about 780MHz instead of 800MHz on some chips. You're right about both formulas being valid depending on how you take the DRAM divider, too. The trouble is that DDR333 is 5/6, due to the original meaning for that divider.
- I cant remember exactly what motherboard or chipset had the divider feature first, but it was in the Pentium 4 Northwood era if I remember correctly. You had various options offered as 6:5, 5:6, 4:3, etc etc. The board would take the ratio and just multiply the FSB by it, to get the DRAM frequency, without any of this formula nonsense (you probably know all this, but bear with me). Some manufacturers labeled them as DDR266, DDR333, DDR400, DDR466, and the rest, depending on what the resultant speed was. Multiplying 200MHz by 5/6 resulted in a speed of 166.67MHz, or DDR333, and from that day on we've been using 5/6 as DDR333, even now the FSB has taken a long walk of a short pier. In keeping with that, you need to use the formula already on the page. --AthlonBoy 15:22, 10 July 2006 (UTC)
Main 939 benefit
The newly filled-in History section (by the way, nice work BorgHunter) states that the main benefit of socket 939 was its 1GHz hypertransport. Surely the dual channel memory controller did more? It has been shown that even a Hypertransport speed of 600MHz is fine, by lowering the HT multiplier, so a small 200MHz bump hardly made the difference. The near-doubling of memory bandwith did, however. I edited the section but it has been reverted because the citation is incorrect, but the citation was a Toms Hardware review of the first 939 parts, and it clearly states that 754 has a single channel memory controller.
Just thought it would be best to put something in the talk page rather than start a revert war.AthlonBoy 21:05, 6 July 2006 (UTC)
- Good catch, that last edit was made in a rush so I wouldn't be late to work. :-P I've added the dual channel mention and included a citation. —BorgHunter (talk) 04:19, 7 July 2006 (UTC)
List of models
Should that list be on the main article, or should we make a subarticle List of Athlon 64 models? I don't much like having it there, but I want some input before I go about moving it. —BorgHunter (talk) 05:00, 8 July 2006 (UTC)
- It might get some objections when (and not if, but when) you nominate this for FA. Also, 47 references is insufficient. There should always be at least 200 references in an article, including a reference to WP:EL for the heading "external links". :-) — Deckiller 05:03, 8 July 2006 (UTC)
- There's already a List of AMD Athlon 64 microprocessors page, so there's no need for a "List of Athlon 64 models" page. One could argue that the list on the Athlon 64 can shrink (or disappear), with the details going on the "List of AMD Athlon 64 microprocessors" page. (The same probably applies to other x86 processor pages, whether Intel or AMD; there are already "List of" pages for several of them.) Guy Harris 07:44, 8 July 2006 (UTC)
"Hardware-set permission levels"
I've been all over the Net trying to get some more information on this "Hardware-set permission levels" business, and unless it's part of Presidio or that virtualisation thing (Pacifica?) can't find anything! Where did this bit of info come from and which 64s is this feature in?
- (Unless that was just a reference to the NX-bit)
- It sounds like you're reading about Data Execution Prevention. DigitalEnthusiast 21:09, 20 December 2006 (UTC)
Mobile Athlon 64
What's this shit about "Mobile Athlon 64" leading to Turion 64? They're two separate processors. The Turion 64 is the low energy consumption one, and the Athlon 64 Mobile was, for a time, the high-performance one that was essentially the desktop processor with SpeedStep added. I know this because I've got a shitty Athlon 64 Mobile in the computer I'm typing this with.
Which is which?
Added "update" tag, some suggestions
I have added the "update" box tag because this article is in need of some serious revision work. As of today (March 2009), the Athlon 64 processor line is no longer produced, but there are passages in the article text mentioning things that "will" happen in 2006 or 2007... We all know that 2 or 3 years are aeons in processor technology. Yet there are still many computers with Athlon 64 processors working very well out there (I am writing this from a 3800+ Venice myself, have no complaints and no need to change to a more recent or faster processor), and the processor series will always have historical value (there are articles on the Zilog Z-80, Motorola 6502 and Intel 8080, after all), so the article is and will remain important.
I am not qualified to make the necessary revisions (I came here to consult the article in the first place) but in addition to the verb tenses and factual updates, there are also two things that, in my opinion, are missing from the article and I would suggest to be added. The first one is a clarification on exactly to what degree is the K10 architecture derived from the AMD64 one used on Athlon 64s, and to what degree one can consider a current Phenom to be a direct descendant of the Athlon 64 series. I suppose this should be more properly explained in the K10 article (it is not, either, at this point - at least not clearly), but I believe it should be at least outlined here.
The second point - perhaps of more interest to some readers - would be the role of each series in the AMD vs. Intel race. As far as I know, the Athlon 64 was the last line of processors that put AMD ahead of Intel in terms of performance. Athlon 64s were faster than Pentium 4s, but Core 2 gave Intel the lead again and K10 has been unable to catch up (at least so far). I think this gives an additional degree of importance to this article, because it also documents an important moment in the history of personal computing. --UrsoBR (talk) 07:25, 26 March 2009 (UTC) AMD Opteron où est mon argent 50,00 $ Popeyes? pour le vendredi? ou vous sera dépensé beaucoup dans le bureau et aucun KUMON pour vous et quatre repas pour seulement 9,95 dollars disparu du dimanche au jeudi !!!!! DSI pas pour vous, non pas la Geek Squad DS fée dieu parents ne peuvent pas vous aider à échapper NA NA NA NA !!!!!!!!! plus vous serez KUMON évanouie parce que vous avez triché et ne vous pour le dîner pie i osez-vous à voler Sempron a été la mise sur le marché nom utilisé par AMD pour les différents processeurs d'entrée de bureau, en utilisant différentes technologies et de la CPU socket formats. Et en plus vous ne pas AMD Opteron pour vous —Preceding unsigned comment added by 18.104.22.168 (talk) 21:48, 17 April 2009 (UTC)
I removed the notice and replaced the text for the section with a summary of the K10 picking up from where the Athlon64 left off, but made note that the Atlon64 arch is still on the market. Defrector (talk) 08:49, 6 September 2010 (UTC)
What is the orignal AMD K8?
When I was a high school student, I heared so many things about his monster, because that was the amazing passing time shifting from 32bit to 64bit computing, and then Apple possessed their most outstanding PowerPC, making our AMD K7 out of mind. Then I read one article about the next coming Hammer processor, I forgot that composition. But the desgin of K8 is much like this, believe or not. That is the original ideas about Hammer rather than the first chipset I got, AMD Athlon 64 2800+. Hammer is the very name arising in the days when Intel released their Hyper-Threading version of Pentium 4, so as one greatest opponent to Intel, the SMT presented on that page is much more possible. And that kinda SMT implementation is just similar with the coming processor with code name "Bulldozer". Suppose when the days Intel were proud of their Hyper-Threading, but there was no similar feature in Athlon 64 processor, how could AMD give one reasonable reply? And if today's AMD K8 is that original K8, why AMD named the it as Athlon64 for those very days. Because AMD name their K5 processors as AMD K5, their K6 as AMD K6, and their K7 as AMD Athlon. So following this convention, it should name it as something else rather than Athlon, such a product during mid-90s. Athlon 64 is just the give-in for that abortion of the original K8 design. Integrated memory controller and even the HyperTransport should not be denoted as the feature or advantage of that microarchitecture. Remember that Hammer was designed to compete with Intel Itanium, but even though the Operon was not the opponent for Itanium at all.
Athlon 64 - consumer-oriented?
I have a bit of a hard time believing that the ORIGINAL Athlon 64 is truly consumer-oriented. I mean, here are my issues:
1. The article says that the Athlon 64 was the "first 64-bit processor to be targeted at the average consumer", and yet EXTREMELY FEW of the original Athlon 64 PCs (around 2004) were aimed at the "average consumer". Almost all of them were essentially high-end workstations, aimed at power users (including the "hardcore gaming" crowd) and obviously at businesses. In nearly every case, they cost over $1000 dollars (in many cases over $1500 dollars, and in either case, the price is higher when adjusted for inflation), and very few of them were aimed at "typical home users".
A typical Intel-based consumer-oriented PC in 2004 had a 32-bit Pentium 4 processor (or Celeron equivalent), whereas a comparable AMD-based PC generally had an Athlon XP (which of course, is 32-bit). And given the extremely small number of consumer-oriented 64-bit programs that were available at the time, this is no surprise to me.
Virtually all of the articles that I have seen from the time period have said that the Sempron was intended for servers, and the Athlon 64 for desktops, but nothing about the Athlon 64 being intended for the "average consumer".
2. If the Athlon 64 was really all that consumer-oriented as such, then why were there so few consumer-oriented PCs that shipped with that processor? And why were there almost no mid-range PCs (in any sense) that shipped with it, especially ones that cost under $1000 dollars?
3. Another issue that I see here is the fact that the 64-bit processors that were available at the time (including the Athlon 64) did not come in a low-end to mid-range version. All of the 64-bit processors available at the time came only in high-end versions, making it even more impractical for nearly all consumers.
4. Unmistakably, the Athlon 64 introduced many new features to the industry. But what use did they have back in around 2004 or 2005? Remember that back then, almost all consumer systems being produced at the time only had about 256 MB of RAM to 512 MB of RAM, and very few consumer-oriented programs used even that much, and many people got on quite fine with 192 MB of RAM, 128 MB of RAM, or even as little as 64 MB of RAM.
Pretty much all programs that really needed the extra performance and RAM upgradability were programs that made heavy use of 3D graphics (such as 3D professional design/CAD software or games aimed at "hardcore gamers"). And technology was also a lot simpler back then also - technologies that we take for granted today such as DVD, video recording (DVD-RW/Blu-Ray), and other such technologies were still catching on, and many people still got on quite fine without them. Even a CD-RW drive was still something that people could live without because of how recent it was at the time.
And there was also no consumer-oriented 64-bit OS available at the time, almost certainly due to the exceptionally small number of home users who had a 64-bit PC at the time. Likewise, the 64-bit version of Windows that was available at the time (Windows XP Professional x64 Edition for workstations and Windows Server 2003 for servers) reflected this by not offering a "Home Edition".
I firmly believe that if there were large numbers of 64-bit PCs aimed at average consumers, as well as relatively inexpensive 64-bit PCs, low-end to mid-range 64-bit processors, and a large amount of people willing to move up to those systems, then Microsoft would have almost certainly included a Home Edition.
But the way it turned out, very few (probably less than 1%) of home users even had a 64-bit PC at all, and so from what I can see, Microsoft likewise reflected this by leaving out the Home Edition in its 64-bit operating system, which in turn meant no 64-bit consumer OS.
5. It is also worth mentioning that even if the Athlon 64 WAS intended to be a consumer-oriented processor, the vast majority of PCs that shipped with it were not aimed at the average consumer as such. The closest that I can think of, personally, is Alienware, and their systems were essentially high-end workstations, but aimed at hardcore gamers and possibly overclockers, with 3D game-style graphics emblazoned over all of their cases.
The only exception to this would be eMachines's systems, since they offered Athlon 64-based PCs that were aimed at typical home users. But they knew how to make a value-oriented PC with much more computing power back then, and that was where they stand out.
So it can be reasoned in this case (if there is any valid evidence for the processor's supposed consumer focus), that the Athlon 64 by itself was a consumer-oriented processor, but that the vast majority of systems that shipped with it were not aimed at the average consumer, and that 64-bit as a whole was not aimed at general consumers.
And again, the problem here was that the 64-bit processors didn't come in a low-end to mid-range version - they were all high-end processors. If a processor only came in a high-end version, is it really aimed at average consumers?
6. If the Athlon 64 was really so "average consumer-oriented" as the pages claim, then why did AMD even have to release the 64-bit Semprons just to extend the market of the 64-bit x86 platform from being a "niche" market to being a mass market for consumers? Wouldn't this be a massive contradiction of terms?
Think about it: If someone supposedly invented a particular model of car to give consumers the ability to drive on diesel fuel rather than gasoline, then why would the same company invent ANOTHER model of car to promote diesel among consumers? Isn't there something a bit inconsistent here?
And the 64-bit Sempron processor actually came in a low-end to mid-range version because that's exactly what the Sempron was, yet no Athlon 64 processor came in a low-end to mid-range version - prior to this, 64-bit processors were only available in a high-end version, whereas almost all home users use low-end to mid-range chips in their computers.
7. The fact that the early 64-bit chips were only available in a high-end version greatly hurt 64-bit's growth, and the lack of mid-range consumer-oriented 64-bit PCs during that time period hurt growth even more. It was not until the Core 2 Duo was introduced that large numbers of people started moving up to 64-bit PCs, and it wasn't even until Windows Vista that it started seeing widespread adoption on the software side (and even wider adoption on the hardware side). Windows XP Professional x64 Edition and Windows Server 2003 were aimed at businesses and power users, whereas Windows Vista was everyone's operating system.
Even as late as 2009, I knew quite a lot of people who still did not have a 64-bit PC at home. It was still quite common not to have a 64-bit PC as late as the late 2000s, and even as recently as 2010, 64-bit was still catching on. It was really with the Core 2 Duo and later Windows Vista (2006/2007 to 2009) that large numbers of people started moving up to 64-bit PCs (both hardware and software), and it was with Windows 7 (2009-2012) that having a 64-bit home PC became ubiquitous (both hardware and software).
Yet I believe that most of this delay could have simply been avoided, had there been a low-end to mid-range 64-bit processor all along, as well as a large enough amount of 64-bit consumer-oriented PCs being produced and distributed during that time period. Just as people could have very similarly adopted Windows NT earlier, had there been a consumer-oriented version prior to Whistler (later Windows XP). — Preceding unsigned comment added by WindowsUser2 (talk • contribs) 01:06, 26 June 2013 (UTC)
Bear, not bare
Hello fellow Wikipedians,
I have just modified one external link on Athlon 64. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20060427091322/http://techgage.com:80/review.php?id=2790 to http://www.techgage.com/review.php?id=2790
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at
Archived sources still need to be checked