Yes, following these instructions, your CPU output will be certainly reduced in the end. This is the CPU utilization history for my machine ( ID 439806) and you will probably want your chart to look approximately the same (few spikes are OK). Are there any flat lines at 100%? Free up more cores. How many cores to free up? How can you be sure that you are doing this right? Open your Task Manager and monitor your CPU utilization. Here it is, under Options->Computing Preferences, use at most 75% of the cores (or any other number you choose). There is an option in your BOINC Manager just for that: And that's bad, you don't want your GPU tasks waiting and stalling, you want them running at full throttle all the time. And if your CPU is 100% busy, then your GPU will have to wait for its turn. To put it simply, there are no pure GPU workloads - the CPU is often needed to provide some 'assistance' with BOINC computations. With your CPU busy all the time, GPU tasks will get stalled often, severely reducing your overall BOINC output. CPU utilization at 100% all the time, that's surely the maximum performance I can get out of my BOINC machine, right? Well, not quite. Typical newbie mistake: load all CPU and GPU cores with BOINC tasks. So choose your GPUs and BOINC projects carefully, if you want maximum performance. In fact, if you check MilkyWay's Top hosts list, you will see that it's populated mostly with AMD 7970s and R9 280X GPUs which are pretty much outdated, but still renowned for their high FP64 performance at affordable prices. Use it for FP32 BOINC projects instead (there are plenty of them). So yes, your shiny new GTX 1080 Ti is able to achieve 10.8 TFLOPS in FP32, but only 0.34 TFLOPS in FP64, so it's a waste of resources to use it for and it will perform terribly there. The majority of BOINC projects use FP32 computations (so called single-precision), but (and some other BOINC projects) require FP64 or double-precision. Unlike simple hashing which is mostly dealing with integer numbers, BOINC (and computational science in general) is dealing with decimal numbers and floating point operations. I've already written about this in one of my previous articles, but it's worth repeating here. Choose your GPU and BOINC project carefully Laurent Domisse, top user, has 107 machines with numerous high-end GPUs crunching for science. I am currently mostly involved with BOINC project and some hints will be relevant only for that particular project, but other hints will improve your GPU performance across all BOINC GPU applications (and maybe even your Proof-of-Work gigahashes, if that's your thing). So, I am going to provide all obvious and less obvious hints on how to squeeze every bit of performance out of your GPUs, maximizing your BOINC output and, in turn, your Gridcoin earnings. Of course, with Gridcoin there is also a monetary incentive to maximize the performance of your hardware: more successfully completed BOINC tasks also mean a larger Gridcoin income. Many BOINC crunchers are carefully studying those lists, comparing performance of their hardware to the performance of other crunchers. Every BOINC project maintains a list of Top Participants, Top Teams and Top Hosts. Welcome to the sixth installment of Gridcoin GPU mining series, continuing our exploration into the world of computational science, done through BOINC network and rewarded through Gridcoin - a cryptocurrency which is rewarding BOINC computations, on top of Proof-of-Stake.Īlthough BOINC is a volunteer effort, it has a very competitive community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |