S
Scott Moore
Yousuf said:
Right answer. Using a machine that cannot address its own installed memory
from an application is sad, and takes us back to 1987, when 386 was used
to run DOS.
Right answer. Using a machine that cannot address its own installed memory
from an application is sad, and takes us back to 1987, when 386 was used
to run DOS.
B
Bill Davidsen
Yousuf said:
I don't hear an answer yet. Assume that 90+% of all computers are NOT
used as servers, game machines, or for engineering calculations. Think
of the majority of systems at home or in the office. What benefit will
any of these people get (ie. pay for) from 64bit? In any sane business
the huge databases are on servers, I can word process a 300+ page manual
on a GB machine and have lots of memory left over, where is the need
that will get people to upgrade?
There was huge pressure for people to move from 16=>32 bits, everyone
hit the limit all the time. I don't see that same driving need today for
most of the market. I don't hear people saying they are going to add
memory, even at $70/GB most peole think they have enough.
And even on servers it's hard to find a benefit for many applications.
The bottleneck is i/o, and even if the hardware could do it I wouldn't
spend the money to put 10TB databases in memory. I can go to 16GB with
32 bits, and the individual processes are only a few MB, so address
space per process isn't an issue.
I expect the change to 64 bit to be quite gradual, done as end of life
replacement rather than upgrade in most cases.
D
David Schwartz
The need will be the things that will be possible on 64-bit platforms
that we don't even think about on 32-bit platforms. For example, you can
'mmap' an entire partition. You can write code that reserves large chunks of
address space for sparse data.
If you don't think 90% of computers are servers or game machines, what
do you think they're doing? I think a lot more than 10% of general-purpose
computers have games as a significant application.
The need will be the things that are easier to do on 64-bit platforms,
and so over time they will only be available on them. But you are right that
the 32-bit limit is not being hit hard, so the change will not be nearly as
swift as the change from 16-bit to 32-bit was, and that change wasn't all
that swift.
Probably so. If you assume memory sizes will want to continue to grow at
the same rate, the average machine will be hitting the 4GB limit pretty soon
now, in about three years if memory serves me.
It won't be long before more new x86 machines have 64-bit capable
processors than don't.
DS
D
Daniel Mandic
But the Industry forgot to move the 16bit programmers, too.
All I see today is 16bit programming with a couple of overlayed programs
(Visual... Virtual..) to program the 32bit machines. Where are the times, of
realtime screen outputs programmed in machine code, or assembler?
Bank Switching? Like the 8bit CP/M machines with some MB of Memory!
Lets Say, 16 times 4GB.
An impossible mission to substitute analogue technik. Even with 512bit (I
suggest Industry having a great number in mind) it could not compare, by
picture quality, to a 70mm Cinemascope. Realtime, and at least 24 pictures a
second ;-)
I would not have one peni left for such a project. That would be, just mad.
Also a today 64bit DVD Player cannot compare to a 45 Years UHF,
air-broadcasted BetaCam or U-Matic Video. Digital is just a dazzling,
jerking picture.
Best Regards,
Daniel Mandic
B
Bill Davidsen
David said:
Sure they can, but what application will benefit from that? I keep
hearing the old song "things we haven't even thought of yet," but we
have had 64 bit Sparc and Power for a decade, and I haven't seen the
common desktop application which is pushing the limits of the memory we
have now. Where's the killer app?
My premise is that somewhere between 75-90% of home and office users
will not need the address space, because the common things are bounded
by the human not the computer. That limits the size of a useful web
page, graphic, etc. Email isn't going to be 4GB, or manuals, and even in
the USA the tax forms won't be that large. You can propose a spreadsheet
of huge size, but it's not easily human usable and generally better
served by a database.
New machines? That sounds possible, the 64 bit capable CPUs are
inexpensive, it's cheap insurance. But people won't be rushing to get
upgrades to 64 bit, their stuff works now.
D
David Schwartz
All of the high-end ones. As soon as it's practical to make an app that
only works on a 64-bit machine, people will do it.
It's not about pushing the limits of the memory, it's about having lots
of address space and using it.
How much data fits on a DVD? How much will fit on a blu-ray or the next
high density storage medium? How much fits on a hard drive today?
I agree. Nothing will dramatically change until it makes commercial
sense to release software that only works on 64-bit. Then people will still
only do that if they get some significant benefit or the 32-bit market is
really small. The more the 64-bit benefit, and the higher percentage of the
target machines that are 64-bit capable, the more likely that 64-bit only
software will be released.
One thing that hasn't been mentioned is the larger register set in
64-bit mode.
DS
T
tk
David Schwartz said:
I think the only reason I would need to upgrade to 64bit in the future
will be software written for it. My guess anyways, I can already do
pretty much all I want on a 3.5 P4E with 2 gigs ram, not weather mapping
here or doing HD encoding yet but DVD encoding works great.
B
Bill Davidsen
Hate to keep asking, but what "high end ones" are those? Outside of BIG
database apps, which are usually server functions rather than user apps,
and high end graphics, which are usually done on dedicated workstations,
I don't see where the benefit will come. And to use all that address
space will require rewriting the applications which now use the 64 bit
file addressing which has been around for about a decade.
I keep hearing that, too, what's the app which benefits?
Which applications read an entire DVD into memory, and why? And other
than a tiny reduction in code complexity, where's the gain? That's a
real gain for a "from scratch" new program, but what vendor will lock
out the 32 bit market by doing it? The gain is not in performance, if
the data doesn't fit in physical memory performance will be limited by
disk speed.
You express my thoughts exactly in that paragraph! I just don't see many
places where there will be a co$t advantage or a performance advantage
with applications which sell in any significant volume. I talked to an
archetect about 64 bit when the UltraSPARC came out, and he said that
the drawing programs were all vector, and took almost no space at all.
That was one place I thought 64 bits would help, and it doesn't.
I doubt that make a difference. There's so much register aliasing in
modern processors that (from what I read) the program logic is more of a
limiting factor. That and the quality of the compilers.
D
David Schwartz
Physics engines such as are used in 3D games. Graphics applications.
Development tools. Encryption. All the applications that don't exist yet
because today's computers can't run them efficiently.
What about the high end graphics, where by high end I mean high end for
what's done on PCs? Things are done on dedicated workstations only when they
can't be done on PCs.
Don't forget, when the '486 first came out, everyone was saying that
nobody would ever need that much power on the desktop. If you give people
the ability to do things, they will want to do them.
Not necessarily. A lot of work can be done by the OS. And the 80/20
rules means that only 20% of the application has to be rewritten to get the
benefit.
All applications that use disks and files. Games. Document preparation
tools. Encryption. Once people can do things, they will insist on being able
to.
That's not the point. The point is that the application may need any
part of the DVD at any time.
It's much more than a tiny reduction in code complexity. Managing a
limited address space is a major PITA.
The gain is also in performance. Not having to view the world through a
narrow window will improve performance as the OS manages the caching rather
than the application, which has a more limited view of system resources and
priorities.
The issue is not what current applications will benefit, but what new
applications will be possible.
More registers will mean you won't need as high a compiler quality to
get the performance. Or, to put it another way, for the same compiler
quality, you can get more performance with more registers.
DS
B
Bill Davidsen
David Schwartz wrote:
This has become pointless, I keep asking for the name or type of
application which any significant postion of desktop users (personal or
business) would find useful enough to justify buying a 64 bit computer
before the normal lifespan of the existing 32 but unit. Haven't gotten
it yet.
I don't expect any rush to 64 bit, when it's cheap and time for a new
computer, then people will go 64 bit. I would guess that means 90% of
the office desktops and 75% of the home units will be 32 bits until they
hit end of useful life.
This has become pointless, I keep asking for the name or type of
application which any significant postion of desktop users (personal or
business) would find useful enough to justify buying a 64 bit computer
before the normal lifespan of the existing 32 but unit. Haven't gotten
it yet.
I don't expect any rush to 64 bit, when it's cheap and time for a new
computer, then people will go 64 bit. I would guess that means 90% of
the office desktops and 75% of the home units will be 32 bits until they
hit end of useful life.
D
David Schwartz
Right, because that's a pointless question.
Before the WWW was invented, you would ask for the application that
would make the ordinary person want to, and be able to, use the Internet.
Nobody could name it.
When the '486 was released, articles said it was so powerful it would
forever be in the server room, never on the desktop. Where were the
applications that would need it?
Of course people aren't using the applications today that require
64-bits to work smoothly because they don't *have* 64-bits. Perhaps in the
near future, people will use 3D rendering software on their desktops that
rival what's now done only in Hollywood. Crazy? Who would have predicted in
1990 that 15 years later people would do desktop publishing on their
desktops comparable to what's done in publishing houses?
Anything that can be done, people will want to do it on their desktops.
And as soon as it's possible, they'll start doing it.
I predict that it will be comparable to the switch from 16-bits to
32-bits. Perhaps slightly slower.
DS
B
Bill Davidsen
David said:
We've had 64 bits for a decade, and the killer desktop apps are somewhat
missing. I'm not holding my breath, the people who do mail and browsing,
maybe their taxes and a "fits on the screen" spreadsheet are the
majority of both personal and business users. Documents, spreadsheets,
E-mail and web pages are limited by people now. Only taxes could be
complex enough to require 64 bits ;-(
Were you around as a participant at that time? The 16 bit systems were
so limited by what you could use and address and do that people jumped
from 16 to 32 bits as soon as they could, and that was "way too long"
for DOS users, much less for the UNIX users of us.
It takes some level of dissatisfaction with what you have to make you
spend, "you" being personal or corporate. Maybe when that killer 64 bit
app comes out. When people are ready to buy a new system anyway they may
go 64 bit if the price is similar. It is at the bottom end and
definitely isn't at the server end.
Save this post, if a killer app comes out which needs 64 bits in two
years, you can reply.
R
Roger Blake
My personal preference is for 36 bits, when I can get them.
D
David Schwartz
Yes. Do you remember how quickly the requirements on typical games went
up? How one year most games required only a 386 and a year later they
required a 486? How long was it after that before 133Mhz or better was
needed?
I just grabbed a random program off my shelf and the box requirements
say "800Mhz Pentium 3 or faster". This would mean your CPU can be no more
than 5 years old *if* it was the very fastest CPU purchased at the time of
purchase! More realistically (few typical users buy the very fastest CPU
available), it means your CPU can be no more than 3 years old.
Right, and that will be the case with 32-bit systems in about three
years as people want to put more than 2Gb (and then more than 4Gb) of memory
in their systems.
All new x86 CPUs except perhaps the very low end will be 64-bit capable
in less than two years. How long do you think it will be before new PCs ship
with a 64-bit operating system by default?
There were ways to handle larger amounts of memory on 16-bit systems
too. It is my bet that at least 15% of commodity software will require a
64-bit CPU and OS within five years.
You are essentially predicting that software requirements will lag
behind hardware availability by an amount that they have never lagged
before. Ever.
DS
D
Daniel Mandic
Hello!
What do you think about 70bit or 72bit OSés. Also this could be a standard.
Maybe a 84 bit OS.
Otherwise, having a DSP kind of Chip would leave it open how the Hardware is
and will work.
Also implementing Kernel structures into hardware would be very Easy with
DSP kind. Better....
I remémber my ZyXEL ISDN modem, started with V.34 (28800). Today it works as
a 56k8 MoDem, too!!!
1994 bought- about 1998 was the 56k8 Software-Update. Just a software which
reconfigures the Hardware being a new MoDem.
Speed is not relevant. Mhz. Bits are interesting and important to get nearer
to reality... But, do you see a difference between a 16Bit Picture and a
32bit?
Otherwise, Making 32bit Sound and 32bit pictures would be a funny plan
.... What hardware could manage such massive dataload in a fine smooth
behaviour?
I mean real 32 bit not 16bit sound on a 32bit machine.Or 24bit pictures...
I think the only interest in 64bit ist the greater RAM access.
Once upon a time 8bit computers made (make) 8bit sounds, 16bit made 8bit and
16bit, 32bit made (make) 16bit and 64 bit is also making 16bit????? Where is
the innovation?
Are the 64bit making (displaying) real 32bit pictures? of 4294967296
possible clours per pixl, not 16777216. This is 4278190080 colurs more. 95%
More.
And please dont tell me something about 24bit Sound. On PC´s it is just
lousy, scratchy and full of noises.
Maybe a 24bit DAT, ok.
Best Regards,
Daniel Mandic
B
Brendan Trotter
Hi,
I think you're missing the difference between "physical addresses"
and "virtual addresses", and the difference between architectural
design and CPU implementation.
The physical address size determines how much RAM (and ROM,
memory mapped devices, etc) a CPU can access. The OS uses this
RAM to create "virtual address spaces" (or fake address spaces)
that other software uses.
For about a decade, 80x86 CPUs have had "physical address extensions"
which allows for 36 bit physical addresses. This limits the amount of
RAM (and ROM, memory mapped devices, etc) to 64 GB (not 4 GB).
The virtual address size is still 32 bit though (or 4 GB), and the OS
usually uses 1 GB or 2 GB for itself, which means applications can
only have up to 2 GB or 3 GB each. This means you can have a
computer with 64 GB of RAM running 32 applications where
each application uses 2 GB (without anything being 64 bit).
All of that is "architectural design" rather than what was actually
implemented though. Back when the 80386 was first designed, Intel
allowed for 32 bit physical addresses in the architectural design,
but (to save everyone money) they didn't implement full 32 bit
physical addressing. They knew no-one would need it (at the time)
so they only implemented 24 bit physical addressing, so that these
CPUs could only access 16 MB of RAM (and ROM, memory mapped devices,
etc).
For a 64 bit CPU, the physical address size is 52 bits and the virtual
address size is 64 bits, but these are the architectural limits which
aren't actually implemented in any 64 bit 80x86 CPU (and probably
won't be implemented for a very long time).
For example, Intel's first 64 bit CPU only implemented 40 bit virtual
addressing and 36 bit physical addressing. AMD's 'Hammer' supports
48 bit virtual addresses and 40 bit physical addresses.
Ironically, the main benefit of "64 bit 80x86" has nothing to do with
being (partially) 64 bit - the additional registers are far more
important and are responsible for any and all performance gains.
Cheers,
Brendan
David Schwartz said:
I think you're missing the difference between "physical addresses"
and "virtual addresses", and the difference between architectural
design and CPU implementation.
The physical address size determines how much RAM (and ROM,
memory mapped devices, etc) a CPU can access. The OS uses this
RAM to create "virtual address spaces" (or fake address spaces)
that other software uses.
For about a decade, 80x86 CPUs have had "physical address extensions"
which allows for 36 bit physical addresses. This limits the amount of
RAM (and ROM, memory mapped devices, etc) to 64 GB (not 4 GB).
The virtual address size is still 32 bit though (or 4 GB), and the OS
usually uses 1 GB or 2 GB for itself, which means applications can
only have up to 2 GB or 3 GB each. This means you can have a
computer with 64 GB of RAM running 32 applications where
each application uses 2 GB (without anything being 64 bit).
All of that is "architectural design" rather than what was actually
implemented though. Back when the 80386 was first designed, Intel
allowed for 32 bit physical addresses in the architectural design,
but (to save everyone money) they didn't implement full 32 bit
physical addressing. They knew no-one would need it (at the time)
so they only implemented 24 bit physical addressing, so that these
CPUs could only access 16 MB of RAM (and ROM, memory mapped devices,
etc).
For a 64 bit CPU, the physical address size is 52 bits and the virtual
address size is 64 bits, but these are the architectural limits which
aren't actually implemented in any 64 bit 80x86 CPU (and probably
won't be implemented for a very long time).
For example, Intel's first 64 bit CPU only implemented 40 bit virtual
addressing and 36 bit physical addressing. AMD's 'Hammer' supports
48 bit virtual addresses and 40 bit physical addresses.
Ironically, the main benefit of "64 bit 80x86" has nothing to do with
being (partially) 64 bit - the additional registers are far more
important and are responsible for any and all performance gains.
Cheers,
Brendan
R
Roland Scheidegger
It's true that the additional registers are the reason for a (small)Brendan said:
performance gain in most common software. However, it is NOT true that
this is resposnisble for "any and all" performance gains. There
definitely is some software out there which indeed can get quite a
massive performance boost from a 64-bit architecture (more than a factor
of 2). Encryption/Decryption software often belongs to that category.
Roland
B
Bill Davidsen
David said:
Oh there were, but they were painful to use in most cases. To address
your main point, it depends on your definition of commodity software,
but by any definition I don't see that as a "killer app" justifying
moving from 32 to 64 bit hardware before the old system is due for
replacement. Actually I would consider that over half of the computers
in desktop use are going to be replaced in 6-7 years, with nothing more
than attrition driving it.
I am. Based on two different justifications. The best is that there
hasn't been a 64 bit killer app for the Mac, and that's been 64 bit for
a decade. The other is that there *is* a point when people have enough
and are not willing to make an upgrade because they don't see the need.
If you can get access to sales info, most 32 bit systems aren't ordered
with max memory, largest disk, or fastest CPU. That certainly suggests
that people don't feel the need.
I'm still confident that 64 bit hardware will come driven by replacement
rather than upgrade. I agree that most computers will include 64 bit
capability, but only because it will be standard. Intel and AMD are
unlikely to spend any money in 32 bit only products, when they need more
performance and lower power foar more.
I predict the big 64 bit software push will be driven by greed, I mean
marketing. When enough people have gotten 64 bit hardware, Microsoft
will suddenly release new versions of all apps, with new features, and
in 64 bit only. I predict they will offer *very* cheap upgrade from 32
bit versions, because they know they will make the money on Windows-64
o/s upgrades. But until most people have the hardware they won't push 64
bit only, because it locks them out of a majority of the market.
As for gamers? I define a gamer as someone who spends at least $100
extra on a computer for memory, faster CPU, or detter display. Oddly,
that lets out a fair percentage of people who do little else with their
computer. If they didn't spend money on hardware at 32 bits, will they
jump to 64 intesad of spending the money on more games? For that matter,
are the games on the 64 bit Mac better? (real question, I have no idea)
D
David Schwartz
No, I'm not missing anything. What you said has nothing whatsoever to do
with what I said. It's *possible* to address an unlimited amount of memory
with an 8-bit CPU, but nobody does that if they don't have to. As soon as
the majority of computers are 64-bit capable, they won't have to, and so
they won't. In any event, the shortage of virtual addresses is the more
serious problem.
PAE is an ugly workaround. A lot of people specifically purchase the
maximum amount of memory their OS can handle without PAE because they want
to avoid it.
DS
C
Cool_X
David Schwartz,
Can you answer a few questions please?
1. Just so I know, what exactly is PAE? (yes, I know what it stands for)
2. What does it do?
3. Why is it a bad workaround?
4. How much RAM can Win 9x, Win NT, 2K and XP, Mac OS 8, 9 and X, and other *nix (assuming
most popular distros) handle without using this "PAE workaround"?
I'm asking these because there are quite a few things I'd never heard of in Brendan's post.
Cool_X
Can you answer a few questions please?
1. Just so I know, what exactly is PAE? (yes, I know what it stands for)
2. What does it do?
3. Why is it a bad workaround?
4. How much RAM can Win 9x, Win NT, 2K and XP, Mac OS 8, 9 and X, and other *nix (assuming
most popular distros) handle without using this "PAE workaround"?
I'm asking these because there are quite a few things I'd never heard of in Brendan's post.
Cool_X