Message boards : News : Experimental QMML WUs
Author | Message |
---|---|
We are experimenting with CPU workunits. Right now they are Linux only. Please note that you may need to install "gcc" in your machine for them to work. More details in the Multicore forum! | |
ID: 48432 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have not been able to get any of the QC tasks for a week now. I have GCC installed. A post said the most recent tasks have had their priority lowered to allow "low reliability" hosts to get work. I am a new member with no credits since I have been unable to get any work. Is my no credit status still preventing me from getting work? | |
ID: 48435 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have not been able to get any of the QC tasks for a week now. I have GCC installed. A post said the most recent tasks have had their priority lowered to allow "low reliability" hosts to get work. I am a new member with no credits since I have been unable to get any work. Is my no credit status still preventing me from getting work? Well GPU work is scarce. Nearly every day I run out. And CPU work is still under testing. ATM there is no work for anyone. http://www.gpugrid.net/server_status.php | |
ID: 48443 | Rating: 0 | rate:
![]() ![]() ![]() | |
as soon as it is working properly there will be lots of work | |
ID: 48447 | Rating: 0 | rate:
![]() ![]() ![]() | |
Well i am running gpugrid/milkyway@home from windows in order to heat my bedroom in a less wasteful way than a stupid electric resistor heating, unfortunately it seems since the beginning of this experiment gpugrid doesn't use much gpu on windows ^^ | |
ID: 48450 | Rating: 0 | rate:
![]() ![]() ![]() | |
Well i am running gpugrid/milkyway@home from windows in order to heat my bedroom in a less wasteful way than a stupid electric resistor heating, unfortunately it seems since the beginning of this experiment gpugrid doesn't use much gpu on windows ^^ I've been heating my home with BOINC for years and I've actually found GPUGrid to have the highest wattage output of most projects. There are multiple ways to increase GPU utilization and therefore not only increase GPU power consumption but a bit more CPU as well. Enabling SWAN_SYNC by searching environment variables in windows search then in the bottom right clicking enviornment variables and adding SWAN_SYNC and changing the 0 to a 1, can yield some better results. Milkyway at home uses the GPU in a very efficient way, taking data from only the GPU cache rather than the GDDR5 memory. The memory uses 15+ watts and is basically unused for the milkyway application. If you want more heat from a backup project consider switching to einstein@home. Einstein also uses quite a bit of CPU to support the GPU computing so this will help with heating. Another option is to buy another nvidia GPU if your motherboard is large enough to support another card. This will definitely be enough to heat your room. | |
ID: 48452 | Rating: 0 | rate:
![]() ![]() ![]() | |
PrimeGrid will heat up a GPU. The GPU boost on my pascal cards is the lowest there meaning it runs the card hard and hits thermal limits. Math projects tend to be the best as they can easily fork to utilize many cores. | |
ID: 48457 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thanks for the responses PappaLitto and mmonnin, everything seems to work again this morning for no particular reasons. +-----------------------------------------------------------------------------+ |.NVIDIA-SMI.388.59.................Driver.Version:.388.59....................| |-------------------------------+----------------------+----------------------+ |.GPU..Name............TCC/WDDM.|.Bus-Id........Disp.A.|.Volatile.Uncorr..ECC.| |.Fan..Temp..Perf..Pwr:Usage/Cap|.........Memory-Usage.|.GPU-Util..Compute.M..| |===============================+======================+======================| |...0..GeForce.GTX.970....WDDM..|.00000000:01:00.0..On.|..................N/A.| |.75%...80C....P2...135W./.180W.|...1345MiB./..4096MiB.|.....91%......Default.| +-------------------------------+----------------------+----------------------+ | |
ID: 48470 | Rating: 0 | rate:
![]() ![]() ![]() | |
Had an 8-core QC unit named c53-TONI_QMML314rst-0-1-RND8160. | |
ID: 48479 | Rating: 0 | rate:
![]() ![]() ![]() | |
Had two units (c71-TONI_QMML314rst-0-1-RND2036_2 and c95-TONI_QMML314rst-0-1-RND7455_2) which reached 69.568% and then stalled out there for a total runtime of 26 and 21 hours respectively. This is on a 8-core i7-6700K running CentOS(effectively RHEL) 7.4. | |
ID: 48481 | Rating: 0 | rate:
![]() ![]() ![]() | |
Had two units (c71-TONI_QMML314rst-0-1-RND2036_2 and c95-TONI_QMML314rst-0-1-RND7455_2) which reached 69.568% and then stalled out there for a total runtime of 26 and 21 hours respectively. This is on a 8-core i7-6700K running CentOS(effectively RHEL) 7.4. I have found that I have to run only one work unit at a time to prevent them from stalling. | |
ID: 48482 | Rating: 0 | rate:
![]() ![]() ![]() | |
Tasks seem to return to 0% completion after BOINC restart in UBUNTU. | |
ID: 48490 | Rating: 0 | rate:
![]() ![]() ![]() | |
Tasks seem to return to 0% completion after BOINC restart in UBUNTU. They return to 1% complete after a reboot for me on Ubuntu. But then, after about 1/2 hour, they go back to where they left off, more or less. I think it is just a startup period that they have to get through first. | |
ID: 48491 | Rating: 0 | rate:
![]() ![]() ![]() | |
@jim thanks! I think I understand now. | |
ID: 48492 | Rating: 0 | rate:
![]() ![]() ![]() | |
By the way, I have found that while running two work units at once seems to always cause problems with stuck work units and errors, running only one at once does not solve all problems. They often still get stuck, but a reboot fixes it. So it seems to be a necessary, but not sufficient condition for my machines to work properly. | |
ID: 48495 | Rating: 0 | rate:
![]() ![]() ![]() | |
Units stuck either at 78.698% or 69.568% with over 1 day processed time and remaining processing time increasing. | |
ID: 48505 | Rating: 0 | rate:
![]() ![]() ![]() | |
Units stuck either at 78.698% or 69.568% with over 1 day processed time and remaining processing time increasing. A reboot usually fixes them, but as noted below they will return to a low value before you see any progress past the point where you left them. EDIT: But I am wondering whether that is "elapsed time", in which case one day is probably too long, or else "CPU time" (shown in parenthesis in BoincTasks). One day of CPU time is not unreasonably long for those percentages, and I would just wait a couple of hours to see if you make progress past those points. They do get stuck there for a while, but temporarily. (That is the problem with running this project. You never know if it is working normally or not.) | |
ID: 48507 | Rating: 0 | rate:
![]() ![]() ![]() | |
I just rebooted one myself that was stuck at 78.698% too long, and it failed. You never know what you will get. | |
ID: 48508 | Rating: 0 | rate:
![]() ![]() ![]() | |
:D | |
ID: 48566 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : News : Experimental QMML WUs