Message boards :
Number crunching :
Too many WUs issued at a time
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 21 Jul 12 Posts: 9 Credit: 433,306,729 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]()
|
Never used to be an issue; but lately your project would issue 3 WUs with a 2 or 3 day completion time on my GPU. I could finish 2 WUs within the deadline but the third would go over. Why has the project started overcommiting tasks? There was no project reset that would alter the expected completion rate to account for a wrong estimate resulting in too many tasks sent at a time. |
|
Send message Joined: 13 Dec 17 Posts: 1419 Credit: 9,119,446,190 RAC: 891 Level ![]() Scientific publications ![]() ![]() ![]() ![]()
|
The project does not determine how many tasks to send to your host. Your host is the only factor in how much work it requests. The project has several types of tasks that it generates with very different estimated runtimes. The acemd3 tasks have made a welcome reappearance and they are very short running currently compared to historical averages for that type. If you need to restrict the amount of work downloaded so that your host can complete it in time with maximum credit, I suggest either reducing the amount of work you request in your host settings or via the website or just create a app_config.xml statement for the project and put in a max_project_concurrent statement. |
©2025 Universitat Pompeu Fabra