By: Dean Kent (dkent.delete@this.realworldtech.com), May 13, 2007 6:04 pm
Room: Moderated Discussions
Doug Siebert (foo@bar.bar) on 5/13/07 wrote:
---------------------------
>
>Somehow I can forsee the discussions in lkml in a few years when the first person
>suggests a mass rename of the x86 arch to x86-32, followed immediately with a discussion
>about whether after that the x86-64 arch should be renamed as x86 :)
As it seems that far too many see this as a dogmatic issue, I would like to pursue it using numbers, as best we can determine them - all references to morons and fools aside...
I don't know all of the numbers, and don't really have time to look them all up so anyone who wishes to provide actual information would be greatly appreciated.
1) The group I was referring to were desktop users, not commercial servers, etc. We can include developers and other 'power users' in the 'desktop users' group, of course.
2) A64 was released around the end of Sept. 2003, IIRC. That is about 3.5 years.
3) Intel released a desktop 64-bit processor in early 2005, IIRC. That is about 2 years.
4) I would guess that the average lifespan of a computer is 5 years, with some people waiting longer to upgrade. I think it would be fair to presume that about 50% to 60% of all computers in use have been upgraded in this time period.
5) AMD has had between 15% and 25% market share during the past 4 years, with a fair percent of that in servers. Desktops have been about 15%, I believe. In addition, not all processors manufactured/sold by them in the past 3.5 years have been 64-bit.
6) I don't know what Intel's mix of 64-bit desktop processors is, but for argument's sake I am presuming no more than 15% to 20% up until fairly recently. If someone has better figures, please present them.
7) If we therefore presume that less than 50% of all systems sold (probably more like 25% or 30%) during the past 3.5 years were 64-bit, and 50% to 60% of all desktops in use were upgraded during this period - that means that 64-bit systems would likely be somewhere between 15% and 20% of the entire market today. Which corresponds neatly with the number I indicated I estimated using our server logs.
8) Most systems under $600 or $700 come with less than 1GB of memory standard. Linus' argument is that 'most' systems are sold with at least 1GB of memory, but I am skeptical of that. I believe that the greatest volume of systems sold will be under $700. These likely don't all come with 64-bit processors, and very likely don't come with a 64-bit OS. Even those with 1GB may not come with one or both of those.
9) The argument has always been that 64-bits is 'free'. Well, I would suggest that if cheap systems have 32-bit processors and OS', while more expensive systems have 64-bit processors and OS' - then it is not free. It doesn't matter *why* it is more, it is a simple fact that it *is*. This, in turn, discourages a certain percentage of people from buying a 64-bit capable system. That will obviously change over time, and possibly a short time - but it is true *today*
10) Since my original skepticism was regarding the assertion that within 'a few years' (perhaps 4 or less?), 64-bits would be so common as to be the default. I don't think you can consider it such until it has *more* than 50% of the *installed* market, and more reasonably 70% or more. If my guesses are close, I think that we won't see such widespread use of 64-bit systems for at least 5 years or more.
11) The vast majority of users only use such applications as browsers, email clients, picture viewers, music players, word processors, tax software, and spreadsheets. Very few are editing pictures (other than doing simple cropping and resizing), and probably won't ever. Even most games that *average* people use are not memory intensive. There is a chance that within 5 years many, if not most, of those users will be doing most of their tasks on a handheld device, and will see little need to upgrade their computer to anything 'fancy' (again - likely to buy low-end systems). Many may just keep their old systems as long as they continue to function.
12) It makes sense that manufacturers of hardware and software would *want* everyone to be using 64-bit systems - because they don't *want* to have two versions of things. It is expensive! So I can fully understand why people in such positions would wave their hands around and say it is *required*.
13) 64-bit drivers are *still* not widely available for many devices, or available at all. If 64-bits was *that* widespread, these devices woult *have* to have 64-bit drivers available. But they don't.
Therefore, the facts seem to indicate that 64-bit systems are still not widely being used, at least not to their full potential (meaning, even if the hardware is capable, the software being used is not).
The fact that there are still *many* systems being sold with 32-bit processors and OS' means that the 'crossover' likely won't occur for more than 3 or 4 years unless something occurs that forces existing users to upgrade to a 64-bit system. My guess is that most people who are hanging on to their systems as long as possible will probably buy the cheapest one they can find to replace it - after all, an old high-end system probably performs worse than even the cheapest low-end systems available (which are likely 32-bit).
I would appreciate it if someone could provide actual numbers (or better ones, at least) that would lead to a different conclusion. I'm a reasonable person, so reason usually works well when trying to convince me.
Now, let me address a couple of nice fallacies that Linus has engaged in (and does so regularly).
1) Prejudicial Language - this is a fallacy whereby one is 'encouraged' to accept the argument because, otherwise they are 'stupid' or 'idiots'. That, of course, does not prove anything except that the speaker doesn't want a discussion, but just wants to silence everyone else. After all, who wants to be considered a fool or an idiot, so who would disagree after such a statement? That is a tactic that I would think should be beneath even Linus. (see how easy it is to use such fallacious arguments).
2) Equivocation - This is where the same word is used in two different ways. For example, I might say "...end users don't require 64-bits". Linus will say "...developers and commercial apps *need* 64-bit addressing, so it *is* required". In the first case, it means that users don't need it to do their typical computing tasks. The second case means that manufacturers must offer a 64-bit model to satisfy *some* users... but it has nothing to do with the first argument.
I'm sure I could find others, but those were the ones that stood out in my mind...
Regards,
Dean
---------------------------
>
>Somehow I can forsee the discussions in lkml in a few years when the first person
>suggests a mass rename of the x86 arch to x86-32, followed immediately with a discussion
>about whether after that the x86-64 arch should be renamed as x86 :)
As it seems that far too many see this as a dogmatic issue, I would like to pursue it using numbers, as best we can determine them - all references to morons and fools aside...
I don't know all of the numbers, and don't really have time to look them all up so anyone who wishes to provide actual information would be greatly appreciated.
1) The group I was referring to were desktop users, not commercial servers, etc. We can include developers and other 'power users' in the 'desktop users' group, of course.
2) A64 was released around the end of Sept. 2003, IIRC. That is about 3.5 years.
3) Intel released a desktop 64-bit processor in early 2005, IIRC. That is about 2 years.
4) I would guess that the average lifespan of a computer is 5 years, with some people waiting longer to upgrade. I think it would be fair to presume that about 50% to 60% of all computers in use have been upgraded in this time period.
5) AMD has had between 15% and 25% market share during the past 4 years, with a fair percent of that in servers. Desktops have been about 15%, I believe. In addition, not all processors manufactured/sold by them in the past 3.5 years have been 64-bit.
6) I don't know what Intel's mix of 64-bit desktop processors is, but for argument's sake I am presuming no more than 15% to 20% up until fairly recently. If someone has better figures, please present them.
7) If we therefore presume that less than 50% of all systems sold (probably more like 25% or 30%) during the past 3.5 years were 64-bit, and 50% to 60% of all desktops in use were upgraded during this period - that means that 64-bit systems would likely be somewhere between 15% and 20% of the entire market today. Which corresponds neatly with the number I indicated I estimated using our server logs.
8) Most systems under $600 or $700 come with less than 1GB of memory standard. Linus' argument is that 'most' systems are sold with at least 1GB of memory, but I am skeptical of that. I believe that the greatest volume of systems sold will be under $700. These likely don't all come with 64-bit processors, and very likely don't come with a 64-bit OS. Even those with 1GB may not come with one or both of those.
9) The argument has always been that 64-bits is 'free'. Well, I would suggest that if cheap systems have 32-bit processors and OS', while more expensive systems have 64-bit processors and OS' - then it is not free. It doesn't matter *why* it is more, it is a simple fact that it *is*. This, in turn, discourages a certain percentage of people from buying a 64-bit capable system. That will obviously change over time, and possibly a short time - but it is true *today*
10) Since my original skepticism was regarding the assertion that within 'a few years' (perhaps 4 or less?), 64-bits would be so common as to be the default. I don't think you can consider it such until it has *more* than 50% of the *installed* market, and more reasonably 70% or more. If my guesses are close, I think that we won't see such widespread use of 64-bit systems for at least 5 years or more.
11) The vast majority of users only use such applications as browsers, email clients, picture viewers, music players, word processors, tax software, and spreadsheets. Very few are editing pictures (other than doing simple cropping and resizing), and probably won't ever. Even most games that *average* people use are not memory intensive. There is a chance that within 5 years many, if not most, of those users will be doing most of their tasks on a handheld device, and will see little need to upgrade their computer to anything 'fancy' (again - likely to buy low-end systems). Many may just keep their old systems as long as they continue to function.
12) It makes sense that manufacturers of hardware and software would *want* everyone to be using 64-bit systems - because they don't *want* to have two versions of things. It is expensive! So I can fully understand why people in such positions would wave their hands around and say it is *required*.
13) 64-bit drivers are *still* not widely available for many devices, or available at all. If 64-bits was *that* widespread, these devices woult *have* to have 64-bit drivers available. But they don't.
Therefore, the facts seem to indicate that 64-bit systems are still not widely being used, at least not to their full potential (meaning, even if the hardware is capable, the software being used is not).
The fact that there are still *many* systems being sold with 32-bit processors and OS' means that the 'crossover' likely won't occur for more than 3 or 4 years unless something occurs that forces existing users to upgrade to a 64-bit system. My guess is that most people who are hanging on to their systems as long as possible will probably buy the cheapest one they can find to replace it - after all, an old high-end system probably performs worse than even the cheapest low-end systems available (which are likely 32-bit).
I would appreciate it if someone could provide actual numbers (or better ones, at least) that would lead to a different conclusion. I'm a reasonable person, so reason usually works well when trying to convince me.
Now, let me address a couple of nice fallacies that Linus has engaged in (and does so regularly).
1) Prejudicial Language - this is a fallacy whereby one is 'encouraged' to accept the argument because, otherwise they are 'stupid' or 'idiots'. That, of course, does not prove anything except that the speaker doesn't want a discussion, but just wants to silence everyone else. After all, who wants to be considered a fool or an idiot, so who would disagree after such a statement? That is a tactic that I would think should be beneath even Linus. (see how easy it is to use such fallacious arguments).
2) Equivocation - This is where the same word is used in two different ways. For example, I might say "...end users don't require 64-bits". Linus will say "...developers and commercial apps *need* 64-bit addressing, so it *is* required". In the first case, it means that users don't need it to do their typical computing tasks. The second case means that manufacturers must offer a 64-bit model to satisfy *some* users... but it has nothing to do with the first argument.
I'm sure I could find others, but those were the ones that stood out in my mind...
Regards,
Dean
Topic | Posted By | Date |
---|---|---|
Rock/Tukwila rumors | mas | 2007/05/05 11:59 AM |
Rock/Tukwila rumors | David Kanter | 2007/05/05 01:33 PM |
Rock/Tukwila rumors | Dean Kent | 2007/05/05 02:35 PM |
K8 vs Win64 timeline | anonymous | 2007/05/05 05:19 PM |
Yes, I misremembered... | Dean Kent | 2007/05/05 09:03 PM |
Rock | Daniel Bizó | 2007/05/06 01:34 AM |
Rock | Dean Kent | 2007/05/06 06:11 AM |
Rock/Tukwila rumors | Joe | 2007/05/06 10:24 AM |
Rock/Tukwila rumors | Dean Kent | 2007/05/06 10:49 AM |
Rock/Tukwila rumors | Linus Torvalds | 2007/05/06 11:09 AM |
Rock/Tukwila rumors | anon | 2007/05/07 12:32 AM |
Rock/Tukwila rumors | Rakesh Malik | 2007/05/07 08:36 AM |
Rock/Tukwila rumors | Michael S | 2007/05/07 09:06 AM |
Rock/Tukwila rumors | anon | 2007/05/07 08:48 PM |
Rock/Tukwila rumors | Rakesh Malik | 2007/05/08 05:45 AM |
Rock/Tukwila rumors | anon | 2007/05/08 04:30 PM |
Wow. (nt) | Brannon | 2007/05/08 05:16 PM |
Rock/Tukwila rumors | rwessel | 2007/05/08 08:48 PM |
Rock/Tukwila rumors | JS | 2007/05/08 09:07 PM |
Rock/Tukwila rumors | JS | 2007/05/09 05:44 AM |
Rock/Tukwila rumors | Rakesh Malik | 2007/05/09 04:35 AM |
Much ado about x | Michael S | 2007/05/09 08:39 AM |
Call it x86-64 | Linus Torvalds | 2007/05/09 09:27 AM |
(i)AMD64 | Michael S | 2007/05/09 11:16 AM |
(i)AMD64 | Linus Torvalds | 2007/05/09 11:29 AM |
(i)AMD64 | Groo | 2007/05/09 03:45 PM |
TIFNAA | anonymous | 2007/05/09 04:49 PM |
Inspired by FYR Macedonia? (NT) | Michael S | 2007/05/09 10:21 PM |
More likely... | rwessel | 2007/05/09 11:39 PM |
TIFNAA | Gabriele Svelto | 2007/05/09 10:57 PM |
(i)AMD64 | James | 2007/05/10 01:27 AM |
i86 | Dean Kent | 2007/05/09 11:30 AM |
(i)AMD64 | Max | 2007/05/09 12:28 PM |
wide86? long86? | hobold | 2007/05/10 04:05 AM |
x87 perhaps, it is one more. :) (NT) | Groo | 2007/05/10 04:50 AM |
x86+ | Dean Kent | 2007/05/10 07:44 AM |
Does it really matter? | Doug Siebert | 2007/05/10 08:10 AM |
let's stay with x86-64 for now, please | Marcin Niewiadomski | 2007/05/10 10:50 AM |
let's stay with x86-64 for now, please | Dean Kent | 2007/05/11 05:11 AM |
let's stay with x86-64 for now, please | rwessel | 2007/05/11 01:46 PM |
let's stay with x86-64 for now, please | Dean Kent | 2007/05/11 05:03 PM |
let's stay with x86-64 for now, please | Michael S | 2007/05/12 09:49 AM |
let's stay with x86-64 for now, please | Dean Kent | 2007/05/12 12:05 PM |
let's stay with x86-64 for now, please | Michael S | 2007/05/12 12:25 PM |
let's stay with x86-64 for now, please | Dean Kent | 2007/05/12 02:39 PM |
let's stay with x86-64 for now, please | JasonB | 2007/05/13 06:43 AM |
client consolidation | Michael S | 2007/05/13 07:37 AM |
let's stay with x86-64 for now, please | Tzvetan Mikov | 2007/05/13 02:44 PM |
let's stay with x86-64 for now, please | rwessel | 2007/05/14 01:42 PM |
What's your point? | Doug Siebert | 2007/05/11 01:56 PM |
What's your point? | Linus Torvalds | 2007/05/11 03:15 PM |
What's your point? | Doug Siebert | 2007/05/13 02:11 PM |
What's your point? | Dean Kent | 2007/05/13 06:04 PM |
What's your point? | JasonB | 2007/05/14 01:06 AM |
What's your point? | Dean Kent | 2007/05/14 06:20 AM |
What's your point? | JasonB | 2007/05/14 03:35 PM |
What's your point? | JasonB | 2007/05/14 06:35 PM |
What's your point? | Dean Kent | 2007/05/14 07:12 PM |
What's your point? | Dean Kent | 2007/05/11 05:06 PM |
What's your point? | Stephen H | 2007/05/13 12:55 AM |
Why didn't MS take advantage of PAE? | David W. Hess | 2007/05/13 07:37 AM |
PAE sucks (Why didn't MS take advantage of PAE?) | Linus Torvalds | 2007/05/13 09:20 AM |
PAE sucks (Why didn't MS take advantage of PAE?) | Dean Kent | 2007/05/13 09:49 AM |
PAE sucks (Why didn't MS take advantage of PAE?) | David W. Hess | 2007/05/13 11:37 AM |
> 1 GB RAM on a 32-bit system | Tzvetan Mikov | 2007/05/13 12:44 PM |
> 1 GB RAM on a 32-bit system | S. Rao | 2007/05/13 02:00 PM |
> 1 GB RAM on a 32-bit system | Tzvetan Mikov | 2007/05/13 04:32 PM |
> 1 GB RAM on a 32-bit system | S. Rao | 2007/05/13 11:19 PM |
> 1 GB RAM on a 32-bit system | Linus Torvalds | 2007/05/13 02:46 PM |
> 1 GB RAM on a 32-bit system | Tzvetan Mikov | 2007/05/13 04:23 PM |
> 1 GB RAM on a 32-bit system | JasonB | 2007/05/13 05:37 PM |
Windows manages memory differently | Tzvetan Mikov | 2007/05/13 07:31 PM |
Windows manages memory differently | JasonB | 2007/05/14 12:50 AM |
Windows manages memory differently | Tzvetan Mikov | 2007/05/14 07:56 AM |
Windows manages memory differently | rwessel | 2007/05/14 02:40 PM |
Windows manages memory differently | David W. Hess | 2007/05/14 03:07 PM |
Windows manages memory differently | rwessel | 2007/05/14 03:51 PM |
Windows manages memory differently | Tzvetan Mikov | 2007/05/14 04:40 PM |
Windows manages memory differently | rwessel | 2007/05/14 05:09 PM |
Windows manages memory differently | Howard Chu | 2007/05/14 10:17 AM |
Windows manages memory differently | Jukka Larja | 2007/05/14 10:30 AM |
Windows manages memory differently | Tzvetan Mikov | 2007/05/14 12:54 PM |
Windows manages memory differently | Howard Chu | 2007/05/15 02:35 AM |
Windows manages memory differently | Groo | 2007/05/15 06:34 AM |
Anyone know what OS X (10.4, Intel, desktop) does? | Matt Sayler | 2007/05/15 05:23 AM |
Anyone know what OS X (10.4, Intel, desktop) does? | Wes Felter | 2007/05/15 07:37 AM |
Anyone know what OS X (10.4, Intel, desktop) does? | Anonymous | 2007/05/15 09:49 AM |
Anyone know what OS X (10.4, Intel, desktop) does? | anon2 | 2007/05/15 06:13 PM |
PAE sucks (Why didn't MS take advantage of PAE?) | Paul | 2007/05/13 02:40 PM |
PAE sucks (Why didn't MS take advantage of PAE?) | Peter Arremann | 2007/05/13 04:38 PM |
PAE sucks (Why didn't MS take advantage of PAE?) | Henrik S | 2007/05/14 02:31 AM |
The fragility of your argument | slacker | 2007/05/13 02:56 PM |
The fragility of your argument | nick | 2007/05/13 04:42 PM |
The fragility of your argument | Howard Chu | 2007/05/14 01:52 AM |
The fragility of your argument | Dean Kent | 2007/05/14 08:19 AM |
The fragility of your argument | anon2 | 2007/05/14 07:26 AM |
The fragility of your argument | Tzvetan Mikov | 2007/05/14 08:01 AM |
The fragility of your argument | Dean Kent | 2007/05/14 08:16 AM |
The fragility of your argument | Linus Torvalds | 2007/05/14 10:57 AM |
The fragility of your argument | JasonB | 2007/05/14 03:48 PM |
The fragility of your argument | Dean Kent | 2007/05/14 06:36 PM |
The fragility of your argument | Ricardo B | 2007/05/16 01:40 AM |
The fragility of your argument | Dean Kent | 2007/05/16 02:32 AM |
The fragility of your argument | Ricardo B | 2007/05/16 05:41 AM |
PS | Ricardo B | 2007/05/16 05:50 AM |
The fragility of your argument | Dean Kent | 2007/05/16 08:07 AM |
Modern web browsing | S. Rao | 2007/05/16 08:16 AM |
Aha! | Dean Kent | 2007/05/16 08:27 AM |
Aha! | Dean Kent | 2007/05/16 08:32 AM |
Aha! | S. Rao | 2007/05/16 09:34 AM |
The fragility of your argument | Ricardo B | 2007/05/16 09:00 AM |
The fragility of your argument | Vincent Diepeveen | 2007/05/16 09:10 AM |
The fragility of your argument | Paul | 2007/05/16 02:01 PM |
The fragility of your argument | Vincent Diepeveen | 2007/05/17 02:05 AM |
The fragility of your argument | anon2 | 2007/05/15 12:35 AM |
Splits vs page allocations? | Matt Sayler | 2007/05/15 06:33 AM |
What's your point? | Michael S | 2007/05/13 07:55 AM |
What's your point? | anonymous | 2007/05/13 10:08 AM |
What's your point? | Michael S | 2007/05/13 10:31 AM |
let's stay with x86-64 for now, please | JasonB | 2007/05/13 06:16 AM |
x864 =) (NT) | some1 | 2007/05/15 02:03 AM |
Rock/Tukwila rumors | IntelUser2000 | 2007/05/06 01:27 PM |
Rock/Tukwila rumors | m | 2007/05/13 07:05 AM |
Rock/Tukwila rumors | mas | 2007/05/15 08:40 AM |