| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project - Phase 2 Forum
Thread: CEP2 server scheduler needs tweaking? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm seeing situations like this occur more often:
----------------------------------------E203009_ 793_ A.26.C21H12S4Se.127.2.set1d06_ 2-- 640 Server Aborted 01/09/11 17:58:20 02/09/11 02:38:50 0.00 0.0 / 0.0 wherein I'm sent a task after it is out to two other people and "just in the nick of time" one of the other people returns it - and I get a server abort.E203009_ 793_ A.26.C21H12S4Se.127.2.set1d06_ 1-- 640 Valid 22/08/11 18:08:46 25/08/11 00:38:35 6.51 156.8 / 142.9 E203009_ 793_ A.26.C21H12S4Se.127.2.set1d06_ 0-- 640 Valid 22/08/11 17:34:04 02/09/11 01:40:54 9.75 129.1 / 142.9 Seems like shouldn't send me the task unless the other wingman has truly "timed out". Usually I ignore them, but now they're happening closer together; got one yesterday, another today. Don't like wasting the electricity. [Edit 1 times, last edit by Former Member at Sep 2, 2011 4:14:16 PM] |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
How would having a task server aborted waste electric? It didn't even run on your system.
The only thing it wastes is a small amount of network bandwidth, and that makes it in the interests of the project to have as few cancellations as possible. If the 2 tasks are returned before you start crunching the resend it should be cancelled. I would even argue that if you are currently running a resend and it gets reported, you should stop running it, return what work you have, get credit for what you did, and get on with the next task. |
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
The wingman is reporting the result after the deadline. The only reason he/she is not getting a "too late" is because the third copy hasn't returned yet. A server abort is a wonderful solution to avoid triplication of effort.
---------------------------------------- Distributed computing volunteer since September 27, 2000 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just a side note, situations like that may occur on any of WCG's projects, not only CEP2.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Dear ibsteve2u,
as far as I can see, this is not an issue with our servers but a late report setting in BOINC. Best wishes Your Harvard CEP team |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Dear ibsteve2u, as far as I can see, this is not an issue with our servers but a late report setting in BOINC. Best wishes Your Harvard CEP team Thanks for the info. The electricity used - were the issue a server problem as I queried, and so the number of incidents I personally saw were actually being multiplied by all CEP2/WCG/BOINC users - would, in fact, have been of significance. So I thought it best to bring them to your attention. I got a couple more of them yesterday, but I'll just interpret them as a statistical anomaly rather than as the massive uptick in the number of server aborts that they appear - from my perspective - to be. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Dear ibsteve2u,
we certainly appreciate every heads-up, in particular on sensitive issues such as minimizing the electricity-footprint of the project. So please keep your thoughts coming. Best wishes Your Harvard CEP team |
||
|
|
|