Message boards :
Number crunching :
CPU versus GPU
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 11 Jul 17 Posts: 20 Credit: 1,429,841,403 RAC: 12 ![]() ![]() |
I just noticed that N-Body Simulation is only CPU. So I checked the box Use CPU. But then I get both CPU & GPU WUs for Separation. Is there any reason to run both CPU & GPU Separation WUs??? Could another option be added to Preferences/Run only the selected applications: ✔ Milkyway@home N-Body Simulation Milkyway@home Separation - CPU ✔Milkyway@home Separation - GPU ![]() |
![]() ![]() Send message Joined: 8 May 09 Posts: 3339 Credit: 524,010,781 RAC: 14 ![]() ![]() ![]() |
I just noticed that N-Body Simulation is only CPU. So I checked the box Use CPU. But then I get both CPU & GPU WUs for Separation. Is there any reason to run both CPU & GPU Separation WUs??? N-body units ARE cpu units, you need to uncheck them to only get gpu workunits. My checkboxes look like this here: Use CPU Use ATI GPU Use NVIDIA GPU Gpu tasks are about 10 times faster at most projects, gpu's have hundreds if not thousands of little tiny cpu's so crunch things much faster if they make the app for them. BUT some projects do not have gpu apps because they say the crunching is not faster because of the way and amount of memory used in the crunching. |
![]() Send message Joined: 11 Jul 17 Posts: 20 Credit: 1,429,841,403 RAC: 12 ![]() ![]() |
This is what I want: ✔ Milkyway@home N-Body Simulation - CPU Milkyway@home Separation - CPU ✔Milkyway@home Separation - GPU ![]() |
©2024 Astroinformatics Group