Re: Is it a bad sign...
- From: "John Thingstad" <jpthing@xxxxxxxxx>
- Date: Fri, 31 Oct 2008 22:36:55 +0100
På Fri, 31 Oct 2008 22:22:33 +0100, skrev George Neuner <gneuner2@xxxxxxxxxxx>:
Other than that it's a trade off. Code expands about 30% using 64-bit
pointers and execution tends to be a slower overall due to memory
bandwidth. OTOH, 64-bit memory management is much better and fixnums
are larger so there is less need for bignums. With floating point you
may not see much difference depending on what 32-bit chip you're
coming from.
This 32 vs. 64 is a bit of a fuzzy area. Most processors today have 64 bit extensions (800 series and up), but run on a 32 bit operating system. But the processor can adapt to to some of the operations in 64 bit internally. This is probably why the difference is not as staggering as one might expect. Also there is the SSEx/XMD and floating point issues. And of course you have to consider internal cache size and supportive hardware like the GPU and IDE/ATA/SATA drive controller etc. Thus metering processor and program performance is becoming increasingly hard and application specific.
--------------
John Thingstad
.
- References:
- Is it a bad sign...
- From: Kenny
- Re: Is it a bad sign...
- From: George Neuner
- Is it a bad sign...
- Prev by Date: Re: Is it a bad sign...
- Next by Date: Re: Symbol clashes: how to avoid them. Part 2
- Previous by thread: Re: Is it a bad sign...
- Next by thread: Convert html diacritics to unicode
- Index(es):
Relevant Pages
|