| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am wondering what the actual benefits of 64-bit applications are. I already know that it allows applications to use ram over the 3 GB area and allows the use of higher addressed registers and ALU's however these would only create minor benefits (From what I understand (other than the ALU's)) to the actual crunching. From what I can see the only real benefits would be from increased pipeline parallelism, increased ALU's, and higher precision so why is everyone releasing 64-bit applications?
----------------------------------------Feel free to be as nerdy in your responses as you want as I am in second year at university studying computing :) and already hold several certificates in the industry. [Edit 1 times, last edit by Former Member at Apr 26, 2011 6:06:57 PM] |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges:
|
Different work (Apps/tasks) use the CPU in different ways and some projects (CEP2) would not benefit to any significant amount at all. On the other hand some projects can utilize 64bit better and will thus benefit (perhaps 10 or 15% faster). So not everyone will be releasing 64-bit applications.
The big thing is the RAM, as you mentioned. But why it's big is because of the number of cores/threads being crunched on. This is increasing. The 3.2/3.5GB limit would get hit very quickly on an x86system trying to run 12 CPU tasks. Throw in a couple of GPU tasks and a few desktop apps and you have no chance. So as long as there is no loss, why not go with a 64bit app? PS. Not too keen on that Primegrid and Collatz pie size. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So 32-bit applications running on a 64-bit operating system can only use the first 3 GB of addressing space?! o.0 I always thought that the operating system allocated the address space dynamically without the application knowing that it was running in such a manner. I guess ive been thinking of the 16-bit emulation layer :P
So that means that even if I have 24 GB of ram The 32-bit applications can only use 3GB total (to share) and all the 64-bit ones will happily have access to as much of the 24 as they need? |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Aedazan,
if you have 24GB of ram running on a 32 bit operating system. Chances are the most memory the operating system will notice is about 3 - 3.5 GBytes. This is on Windows. If you are running Linux with pae kernel than that goes up quite a bit. If you have 24 GB of ram on a 64 bit operating system. then it'll recognize all 24 GB for processes. I think that goes up to 4TB of RAM. Now if you were running 32 bit applications, then each process can use up to 2 GB of memory. So, say you were running 64 bit os you could then run 12 32 bit processes that were using up the max memory. With that said, none of our applications use anywhere near that value. Here is a reference on windows and the limitations for memory and operating system bits. http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx -Uplinger |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges:
|
Windows 7 Ultimate, Enterprise and Professional can all go up to 192GB physical memory, in theory. Vista is 128GB.
The real limiting factor is the motherboard. This is typically 8GB, 12GB, 24GB, 32GB, 64GB or 128GB. Even on servers, expansion boards are often needed to go past 32GB. W7 Home Premium can handle 16GB RAM, which is plenty for most people. Even Home Basic can use 8GB RAM which is fine for all but the most multitasking home user. Starter edition should be avoided though; 2GB limit! The biggest Boinc task I see is the Lattice Projects; running a 1.5GB Garli. |
||
|
|
|