- Firefox windows 8.1 64 bit 1080p#
- Firefox windows 8.1 64 bit upgrade#
- Firefox windows 8.1 64 bit code#
And remember that all new 圆4 are useless if the cpu can’t read it or it needs converted to machine code (which also takes a lot of processing power/speed)ĭon’t believe the am going to have to catch you there on your assertion, that is a common misconception, having 64bit version of a program running on a 64bit system will not necessarily make it run any faster as opposed to a 32bit program running on a 32bit system, simple due to having more bits, however, it will prevent your programs from slowing down due to the RAM limitations of standard 32bit systems. So in the real world there is no benefit from it, it’s more theoretically or only in some benchmark which use features that x86 doesn’t support. And of course the is always the backwards compatibility problem which will never be cutted because this will break some extensions. It decency how the build was compiled, which settings do you use with that browser and how many extension/plugin/external stuff you load. > It’s also worth bearing in mind that a 64-bit build can be compiled to take advantage of newer processor features that will in itself make the program faster.Īs I wrote in the real world it isn’t faster at all, because the new extensions does not have much effect on “browsing speed” or the browser itself, you can benchmark yourself with the current nightly’s, x86 is for me faster and this “optimized 圆4 builds” and that’s with a 圆4 processor. Don’t get me wrong but that “圆4 feature” is useless and the browser should be more focus on the security (always), it would be better to integrate an downloader database with hips (so no av needed anymore) or something like that but as always, hype is all about ….ītw Shumway works already good together with 圆4, most plugins which have backwards problems only need to change the paths and nothing else (if they are not native 圆4 ones) to solve the problems and since we can edit the. I’m using the nightlys since the beginning and the only problem are the backward compatibility and the installer but I’ve not understand why that take so long to “fix”, the plugin-container already works as a wrapper since v30 or less and it wouldn’t be that hard to separate two processes, one for x86 and one for 圆4. And I’m power user, the normal user not open 100 tabs every time…. I can use 100 tabs with 100x html5 content and it still not reach the 4gb wall. If you Browser needs more than 4GB you definitely doing it wrong or the browser take to much ram for nothing. The only news is that it will be finally available for all at v37 and I still don’t get the point why we need such things in 64-Bit.
Firefox windows 8.1 64 bit upgrade#
Maybe it’s time to upgrade your hardware?Ħ4-Bit nightlys exist since 2004 on the ftp-server, so that’s not a news at all.
Firefox windows 8.1 64 bit 1080p#
I currently run Chrome v.7 dev-m, and Nightly 35.0a1 () both are 64b versions under Windows 7-64b with hex-core CPU running at 4.1Ghz, 16Gb DDR3 RAM, and a 2Gb nVidia GT610 video card I overclock from stock 810Mhz to 1020Mhz which provides excellent 1080p gaming at 50fps.
To hit over 1,600,000k I’d have to have over a dozen tabs open. The moment I visit a link, the base foot print changes to just under 400,000k – depending on how many extensions are being used on that page? and for each tab I open it adds another 50,000k – 150,000k per tab. For me running Nightly 64b, and Chrome DEV-64b, Firefox runs just under 300,000k while Chrome where I have installed the same amount of extensions (15) as in Firefox runs the base program at just over 300,000k and each plug-in runs between 20,000k to just over 260,000k (Ad Block Plus) for a grand total of just over 1,600,000k. ? Firefox runs as a single operation, while Chrome runs each installed extension and plug-in as a separate process.
0 kommentar(er)
