Many Linux distros provide their own 64 bit builds of Firefox, Thunderbird, and SeaMonkey in their repositories.Ħ4 bit builds for Mac OS X are available at. A 64 bit version might be faster due to it being optimized for CPU's that support x86-64 (it has twice as many general purpose registers and SSE/SSE2 registers as a x86 CPU, and they're all twice the width).Ħ4 bit builds for Linux are available at.Code that uses large data types (64/128 bit WORDs) will be faster because you don't need to play the 'split it into 32 bit WORDs' game.Code that is not careful about memory packing/alignment can run less efficiently as 64 bit.The effective processor cache size will also be reduced. 64 bit pointers are larger than 32 bit pointers, so there's more memory to move around, causing a potential performance hit. Code that uses a lot of pointers will consume more memory.This updated blog post benchmarks 32 and 64 bit versions of Firefox, including Waterfox (specifically compiled for 64-bit) and concludes that " We should see some performance improvements in the future, but Firefox 64-bit doesn’t appear to give you a faster browsing experience at this time." This Ghacks article compares 32 and 64 bit versions of popular browsers and concludes " Most differences are marginal and not visible to the user. Typically you only want to use a 64 bit version if the application exceeds the 4GB virtual memory space limit. If you had poor performance before you might not notice any improvement. However, unless the the application is able to take advantage of the wider registers (typically multimedia encoding/decoding, cryptographic, or number crunching applications), you may not see any performance improvement. You can run a 32 bit version of a Mozilla application using a 64 bit kernel (Windows 7 圆4 etc.) though a 64 bit version "supposedly" increases performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |