Quote:
Originally Posted by Shadowex3
Axel if you're going to go against benchmark results and even common sense that much, especially if you're going to claim that somehow being 64bit is going to make something take more memory than if it were merely 32 bit, i'm going to need some citations.
|
A 64 bit application will always use more memory. Not always going to be significant but it will. Ignoring the data being stored even, the address of each variable will take up 8 bytes of memory on a 64-bit machine vs 4 bytes on a 32-bit machine. This is magnified by the data taking up additional space. Again a long integer will take up 8 bytes vs 4 bytes. There are ways of mitigating this but no on in their right mind will go through the hassle unless the app is using a huge chunk of data. I've had to do it and its not fun.
There are applications that will see a performance degradation when they are converted to 64-bit. This is usually due to things like increased mathematical complexity, increased loads on hardware and changes in timing. A developer who understands 64-bit development can usually correct these.
I've been doing 64-bit development and converting of 32-bit applications to 64-bit for several years and I've seen the full gamut of improvements and degradations caused by 64-bit apps.