CaedenV
Splendid
[citation][nom]JOSHSKORN[/nom]Yes and this is unfortunate. We need more competition in the 64-bit browsing world. I currently use Waterfox. It's only other competition (that I'm aware of) is IE 64-bit.[/citation]
forgive my ignorance, but what advantage could 64bit bring to web browsing?
I know at an OS level it allows for more ram utilization, more precise calculations, and occasionally more advanced commands... but in reality the only one that really makes a big difference is the Ram address issue for most people.
On the side of the browser you typically do not need more memory usage. You would think that 4GB per process would be plenty considering you can hardly get 1.6GB of total use out of 40 tabs. If a web page is requireing 64bit calculations (something that you pretty much never see except in extremely specialized workloads), it would almost always be better for the web designer to take the workload and have it processed on the server, providing a result in the web browser, rather than having the web browser and client machine (which is poorly optimized for the task) to such things.
On the last part I am going to have to plead ignorance. My understanding is that when you move to 64bit that most instructions are still 32bit instructions... but with a bunch of empty space tacked on to them to make them '64bit', and that optomizations can be made by tacking 2 instructions together so that they get processed at the same time, or that a more advanced or newer instruction can be made in that 64bit space which can do things in one step instead of 2 steps. But in the real world we rarely see such performance increases. I see the improvements in heavy multitasking due to the extra RAM being available, but given the same general workload using sub 4GB of ram it feels like there is no appreciable performance difference between 32 and 64bit.
Perhaps I am wrong? Please let me know if I am missing something.
forgive my ignorance, but what advantage could 64bit bring to web browsing?
I know at an OS level it allows for more ram utilization, more precise calculations, and occasionally more advanced commands... but in reality the only one that really makes a big difference is the Ram address issue for most people.
On the side of the browser you typically do not need more memory usage. You would think that 4GB per process would be plenty considering you can hardly get 1.6GB of total use out of 40 tabs. If a web page is requireing 64bit calculations (something that you pretty much never see except in extremely specialized workloads), it would almost always be better for the web designer to take the workload and have it processed on the server, providing a result in the web browser, rather than having the web browser and client machine (which is poorly optimized for the task) to such things.
On the last part I am going to have to plead ignorance. My understanding is that when you move to 64bit that most instructions are still 32bit instructions... but with a bunch of empty space tacked on to them to make them '64bit', and that optomizations can be made by tacking 2 instructions together so that they get processed at the same time, or that a more advanced or newer instruction can be made in that 64bit space which can do things in one step instead of 2 steps. But in the real world we rarely see such performance increases. I see the improvements in heavy multitasking due to the extra RAM being available, but given the same general workload using sub 4GB of ram it feels like there is no appreciable performance difference between 32 and 64bit.
Perhaps I am wrong? Please let me know if I am missing something.