Message boards :
Number crunching :
Missing deadline on long run tasks
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 25 Dec 09 Posts: 8 Credit: 246,817,898 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Having a problem where long run tasks are not being completed in time by my 5400M. Used to be slow but otherwise worked fine. Is there a setting that can be changed so my crunching capability is better represented so only tasks I will actually be able to finish timely come to me? |
|
Send message Joined: 5 May 13 Posts: 187 Credit: 349,254,454 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Some of the Long tasks are just too demanding for your GPU. I can't just say "disable Long tasks", since many of them - maybe most - can be completed in time (before the deadline) by your card. But I do urge you to check on the progress of every Long task you run. You have to determine which Long types of task your card can complete in time and which it cannot. That way, when you receive a task you know you can't complete in time, you will have the chance to abort it and avoid crunching for almost a week (!) without getting any credit at all! There's also another matter, your GPU gets sizzling hot! That NOELIA_MG2EC you completed a few days ago reports 92-93C for your GPU, that's just too much! Poor thing!
|
|
Send message Joined: 25 Dec 09 Posts: 8 Credit: 246,817,898 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Actually, I have not seen a long run task complete on the laptop in time for quite a while. The short runs seem to be OK. Maybe I will disable long runs on the laptop only of that is possible. I have a desktop with two small but otherwise capable GPUs that seem to be fine with anything thrown at them. |
|
Send message Joined: 25 Dec 09 Posts: 8 Credit: 246,817,898 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
See the setting but it looks like it will disable long runs for all machines. Guess I will just go with the abort if unable you suggested earlier. Thank you! |
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 351 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
See the setting but it looks like it will disable long runs for all machines. Guess I will just go with the abort if unable you suggested earlier. You can set up to four different 'locations' (sometimes descibed as 'venues', from an old BOINC terminology), and create a complete set of preferences - including the 'long run'/'short run' choice - for each location. Set up an unused location to be 'short runs only', and set the computer that is having trouble keeping up to that location. |
©2025 Universitat Pompeu Fabra