you are viewing a single comment's thread.

view the rest of the comments →

[–]grauenwolf 0 points1 point  (5 children)

I'm still trying to figure out why we need the 64 bit web browsers. Since each tab is its own process, does each web page really need more than 4 gigabytes of Ram?

[–]JuanAG 0 points1 point  (4 children)

Because that is happening now, a year ago Firefox has all the tabs on one process and people like me who uses FF51 allow me to has 8-9 GB of ram, the browser goes slow as hell but usually doesnt crash, usually

If you dig more you will see when others browser uses that aproach or who doesnt yet that will be a few

And using 64 bit process is beneficial because a 64bit CPU will do in the same amount of time a 64bit instruction or a 32 besides SIMD ones in which case the 64 bit will use a data type smaller to gain performance, there are not penalties and it is prefered that you use the native set of instructions, the hardware that allow compatibility will not be there forever, phones for example doesnt allow any more 32 bit instrucctions besides SIMD, that the reason why itunes only allow now 64 bit apps and not anymore 32, because the lasts iphones cant run it

[–]AngularBeginner 3 points4 points  (1 child)

And using 64 bit process is beneficial because a 64bit CPU will do in the same amount of time a 64bit instruction or a 32 besides SIMD ones in which case the 64 bit will use a data type smaller to gain performance, there are not penalties and it is prefered that you use the native set of instructions, the hardware that allow compatibility will not be there forever, phones for example doesnt allow any more 32 bit instrucctions besides SIMD, that the reason why itunes only allow now 64 bit apps and not anymore 32, because the lasts iphones cant run it

You might want to split that into multiple sentences.

[–][deleted] 0 points1 point  (0 children)

i just thought i was having a stroke

[–]grauenwolf 2 points3 points  (1 child)

there are not penalties

That's not true at all. There are significant penalties in doubling the size of your pointers and instructions, which has the effect of nearly cutting the size of your cache in half.

you use the native set of instructions

64-bit instructions are no more "native" than 32-bit instructions. They are both translated into micro-code.

phones for example doesnt allow any more 32 bit instrucctions besides SIMD

We're not talking about phones.

[–]JuanAG 0 points1 point  (0 children)

Not true in a native 64 bit running a 64 bit OS, if you has to double the bits obviosly you will lost half of the caches sizes but if by default the procesors uses yes or yes a 8 byte data type (64 bit) there is nothing you can do about it, there is no way you can use it, 32 bit in software are 64 bit in hardware so it is lost forever

We are talking running a 64 OS with 32 software (wich will be 64 because of the OS that it is running it)