Author |
Message |
PaulSend message
Joined: 25 Apr 13 Posts: 26 Credit: 226,100,832 RAC: 260,269 Level
Scientific publications
|
Used to have several running at once. Now, for the past several weeks, nothing. I've even expanded the amount of disk space for GPU. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
Used to have several running at once. Now, for the past several weeks, nothing. I've even expanded the amount of disk space for GPU.
The only work available is the ATMbeta tasks of which there has been plenty for weeks.
Do you have those tasks selected in Preference along with the mandatory accept beta tasks? |
|
|
PaulSend message
Joined: 25 Apr 13 Posts: 26 Credit: 226,100,832 RAC: 260,269 Level
Scientific publications
|
Beta tasks? |
|
|
PaulSend message
Joined: 25 Apr 13 Posts: 26 Credit: 226,100,832 RAC: 260,269 Level
Scientific publications
|
Couldn't find anything saying Beta. |
|
|
|
Couldn't find anything saying Beta.
go here: https://gpugrid.net/prefs.php?subset=project
and edit your preferences to
"Run test applications" = yes
and make sure the checkbox for "ATM (beta)" is selected
"test" = "beta"
____________
|
|
|
PaulSend message
Joined: 25 Apr 13 Posts: 26 Credit: 226,100,832 RAC: 260,269 Level
Scientific publications
|
Thank You! It worked, have 2 tasks now. Any other suggestions welcome. Your replies aren't notifying me, only if I happen to logon. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
Read the main thread on these tasks in News >> ATM
https://www.gpugrid.net/forum_forum.php?id=24
They cannot be stopped or they error out.
Tasks with naming convention 2-5 through 5-5 will show 100% completion when started, this is normal, so just let them run until they finish.
The tasks DO NOT checkpoint. |
|
|
PaulSend message
Joined: 25 Apr 13 Posts: 26 Credit: 226,100,832 RAC: 260,269 Level
Scientific publications
|
I have over a TB of space for GPU, but no projects. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
Current tasks are still the few acemd and the new Quantum Chemistry on gpu tasks.
There was a big slug of them released this morning. All gone now.
You need test applications selected and ALL applications in project preferences to get them.
https://www.gpugrid.net/forum_thread.php?id=5429 |
|
|
|
There are WUs in progress but for about a month they always go to someone else. I wonder if I need to set BOINC to not run other projects atm, or some kind of nag addon to BOINC that makes it hammer the server for requests every minute or so. We don't seem to be getting work to those who don't have tasks already.
____________
|
|
|
|
There are WUs in progress but for about a month they always go to someone else. I wonder if I need to set BOINC to not run other projects atm, or some kind of nag addon to BOINC that makes it hammer the server for requests every minute or so. We don't seem to be getting work to those who don't have tasks already.
I had the same issue, nothing for over a month despite others getting constant tasks and despite creating an aggressive 'request work' script for gpugrid.
But I think I've found the reason - and it may apply to you, or at least it couldn't harm to check.
When I enabled the 'work_fetch_debug' flag in the BoincMgr event log, I noticed messages saying "tasks won't finish on time". When I checked my computer details on gpugrid.net, the 'task duration correction factor' was set to a ridiculously high value.
Solution: removed gpugrid project from my BoincMgr, deleted the computer record in my account on gpugrid.net, reattached and hey presto! Got a workunit!
Worth a try? |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
Probably a holdover from previously running the acemd tasks.
You needn't have to resort to such drastic procedures of removing BOINC and the project.
The task_duration_factor is simply a parameter value in the client_state.xml file.
You could have just stopped BOINC and edited the dcf value for GPUGrid in its section.
I just set dcf values to 0.01 for all my projects. For the projects that still use the dcf parameter, any new tasks will simply recalculate from that low value to what the true dcf value for the ATMBeta tasks really are.
But be advised, the dcf value applies to ALL the applications in a project. Changing to a different app than what you were running will and can produce a large variance in the dcf value simply because one app may be more efficient than another app.
Which puts you right back into your original issue of not getting work because BOINC thinks you can't finish in time.
Solution then is to just edit client_state.xml again back to a low dcf value. |
|
|
|
Probably a holdover from previously running the acemd tasks.
You needn't have to resort to such drastic procedures of removing BOINC and the project.
The task_duration_factor is simply a parameter value in the client_state.xml file.
You could have just stopped BOINC and edited the dcf value for GPUGrid in its section.
I just set dcf values to 0.01 for all my projects. For the projects that still use the dcf parameter, any new tasks will simply recalculate from that low value to what the true dcf value for the ATMBeta tasks really are.
But be advised, the dcf value applies to ALL the applications in a project. Changing to a different app than what you were running will and can produce a large variance in the dcf value simply because one app may be more efficient than another app.
Which puts you right back into your original issue of not getting work because BOINC thinks you can't finish in time.
Solution then is to just edit client_state.xml again back to a low dcf value.
It seems to be a bit more complicated than that. I tried the client_state.xml route several times before, without any success.
Now, after that single windows task which predictably failed - see the News section topic for that - I once again get "won't finish in time" messages.
Even though my dcf is still at 1...
It could also be an issue in the expected flops/task settings for windows tasks.
In any case, when I began crunching ATM tasks some months ago, I used to get dozens of tasks without issue, then one day that changed and the "on time" issue started. Strange...
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
Make sure you actually have run BOINC benchmarks on your host. If you don't, the client will report the default low 1,000,000 FLOPS value for the host.
That will produce erroneous estimated calculation times. |
|
|
|
Make sure you actually have run BOINC benchmarks on your host. If you don't, the client will report the default low 1,000,000 FLOPS value for the host.
That will produce erroneous estimated calculation times.
I'm at 5000+ million flops and 25000 million iops, so a fair bit higher than your computers, with a dcf of 0.01 and still get "won't finish on time" messages...
https://www.gpugrid.net/show_host_detail.php?hostid=617069
Any other theories? |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.
The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.
I would have to scour the hosts and see if I could find someone else running that card to compare times.
I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.
The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.
Granted Linux is always faster than Windows.
Don't have any other theories for your experience now. |
|
|
|
Any other theories?
Yes.
Try setting "Store at least XX days of work" parameter as low as possible for BOINC Manager to start requesting for GPU work.
A detailed explanation can be found at Message #54300. |
|
|
|
The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.
The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.
I would have to scour the hosts and see if I could find someone else running that card to compare times.
I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.
The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.
Granted Linux is always faster than Windows.
Don't have any other theories for your experience now.
On average, my 1080Ti took 5hrs to complete an ATM WU, so I completed just shy of 5 WU's per day. This was back in October, when I still received them. So GPU age/performance is definitely not the issue. Unless of course they changed the WU size recently.
|
|
|
|
Any other theories?
Yes.
Try setting "Store at least XX days of work" parameter as low as possible for BOINC Manager to start requesting for GPU work.
A detailed explanation can be found at Message #54300.
Allright! Now that is excellent advice, as I did indeed increase my work buffer at some point. And it did the trick allright, I got new WU's now.
Thanks, man! |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.
The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.
I would have to scour the hosts and see if I could find someone else running that card to compare times.
I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.
The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.
Granted Linux is always faster than Windows.
Don't have any other theories for your experience now.
On average, my 1080Ti took 5hrs to complete an ATM WU, so I completed just shy of 5 WU's per day. This was back in October, when I still received them. So GPU age/performance is definitely not the issue. Unless of course they changed the WU size recently.
Yes, Steve said they did indeed increase the size of the tasks so they run longer now. Was only 50 atoms originally and is now doubled to 100. |
|
|
|
Yes, Steve said they did indeed increase the size of the tasks so they run longer now. Was only 50 atoms originally and is now doubled to 100.
I think that was even earlier, before October, because judging from the WU I coerced into running now (through some job.xml/run.bat shenanigans ;-) ) I will still finish in less than 5 hours.
1 hour runtime now and already at 22% |
|
|
mrchipsSend message
Joined: 9 May 21 Posts: 16 Credit: 1,410,851,247 RAC: 696,388 Level
Scientific publications
|
Can someone get some Window tasks onto the project so most of us can do some work?
____________
|
|
|
PascalSend message
Joined: 15 Jul 20 Posts: 78 Credit: 1,916,125,875 RAC: 9,707,312 Level
Scientific publications
|
pour avoir du travail en permanence il faut tout cocher sur les préférences du compte et passer sous linux.
to have work constantly you must check everything on the account preferences and go under linux.
____________
|
|
|
PascalSend message
Joined: 15 Jul 20 Posts: 78 Credit: 1,916,125,875 RAC: 9,707,312 Level
Scientific publications
|
j 'ai choisi linux mint car c'est le plus simple et plus complet.J'ai testé ubuntu hier et c'est pourri.une fois linux mint installé,faire les mises a jour systeme et driver.
ouvrir un terminal et taper ce qu'il y écrit en dessous ligne apres ligne.
pour installer boinc
sudo add-apt-repository universe
sudo apt update
sudo apt upgrade
sudo apt install boinc
sudo usermod -aG boinc your_username_here
Redémarrez la machine
sudo systemctl enable --now boinc-client.
je conseille aussi d'installer boinctasks js ou boinctasks avec wine pour surveiller boinc.
your username here dans la 5 eme ligne doit etre remplacer par votre nom d'utilisateur(exemple pascal pierre ou john).
respecter l'espace apres le mot boinc sur la meme ligne.cela parait évident pour les connaisseurs linux mais pas pour un néophyte
I chose linux mint because it is the simplest and most complete.I tested ubuntu yesterday and it’s pourri.Once linux mint installed, do the system updates and driver.
open a terminal and type what he writes below line after line.
to install boinc
sudo add-apt-repository universe
sudo apt update
sudo apt upgrade
sudo apt install boinc
sudo usermod -aG boinc your_username_here
Restart the machine
sudo systemctl enable --now boinc-client.
I also recommend to install boinctasks js or boinctasks with wine to monitor boinc.
your username here in line 5 must be replaced by your username (example pascal pierre or john).
respect the space after the word boinc on the same line.it seems obvious to linux connoisseurs but not for a neophyte
____________
|
|
|
PascalSend message
Joined: 15 Jul 20 Posts: 78 Credit: 1,916,125,875 RAC: 9,707,312 Level
Scientific publications
|
une derniere chose quand vous installer linux mint,il faut garder une seule carte graphique dans l'ordinateur autrement l'installation plante.vous pouvez remettre les autres gpu apres les mises a jour systeme et driver.
just last thing when you install linux mint,you have to keep a single graphics card in the computer otherwise the installation crashes.you can put the other GPUs after system and driver updates.
____________
|
|
|
PascalSend message
Joined: 15 Jul 20 Posts: 78 Credit: 1,916,125,875 RAC: 9,707,312 Level
Scientific publications
|
ne pas oublier d'installer oracle virtualbox pour les projets comme lhc@home ou rosetta.
don’t forget to install oracle virtualbox for projects like lhc@home or rosetta
____________
|
|
|
mrchipsSend message
Joined: 9 May 21 Posts: 16 Credit: 1,410,851,247 RAC: 696,388 Level
Scientific publications
|
i tried Linux Mint - mozilla won't work, firefox won't work
COMPLETE waste of time - PLEASE LOAD WINDOW TASKS.......
____________
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1360 Credit: 7,912,140,522 RAC: 5,676,538 Level
Scientific publications
|
i tried Linux Mint - mozilla won't work, firefox won't work
COMPLETE waste of time - PLEASE LOAD WINDOW TASKS.......
I would recommend you try Ubuntu over Mint anytime. Much less hassle and guaranteed to work with Boinc. |
|
|
PascalSend message
Joined: 15 Jul 20 Posts: 78 Credit: 1,916,125,875 RAC: 9,707,312 Level
Scientific publications
|
bonjour chez moi c'est le contraire .tout fonctionne sur linux mint sans probleme mais avec ubuntu le store debian ne fonctionne pas.
J ai trouvé cette commande en esperant que ça marche.
ps -e | grep snap-store #id blocking process
kill #id
sudo snap refresh
hello to me it’s the opposite. everything works on linux mint without problems but with ubuntu the debian store does not work.
I found this command hoping it would work.
ps -e | grep snap-store #id blocking process
kill #id
sudo snap refresh
____________
|
|
|