Just curiosity why this WU get so few credit (takes mote than 40K sec to process on my host and 145k sec on the wingmen host) and why it was processed by two hosts?

http://www.gpugrid.net/workunit.php?wuid=4537204

---

Just curiosity why this WU get so few credit (takes mote than 40K sec to process on my host and 145k sec on the wingmen host) and why it was processed by two hosts?

http://www.gpugrid.net/workunit.php?wuid=4537204

It took your wingman, more than 24 hours to complete so no bonus. But eventually your wingman reported the WU earlier than you did, so no bonus for you as well. Credits are granted evenly to all rigs.

---

Greetings from TJ

Just curiosity why this WU get so few credit (takes mote than 40K sec to process on my host and 145k sec on the wingmen host) and why it was processed by two hosts?

http://www.gpugrid.net/workunit.php?wuid=4537204

It took your wingman, more than 24 hours to complete so no bonus. But eventually your wingman reported the WU earlier than you did, so no bonus for you as well. Credits are granted evenly to all rigs.

Thanks TJ.

That i allready understand but why the WU was sended to my host to crunch before thewingman expiration date? (the wingman WU was sended few days before and not expired) if in theory minimum quorum 1 and initital replication 1 parameters shows there are expected to send only to 1 host? and only send to a new host if the WU have any processing problem (error or expiration).

---

...but why the WU was sended to my host to crunch before thewingman expiration date?

Not quite...It looks to me like you were sent the task (almost) 2 hours after your wingman's 5-day expiration was up. By that time, he had probably started to run it, so his task wasn't cancelled. From there, what TJ said... :-)

---

...but why the WU was sended to my host to crunch before thewingman expiration date?

Not quite...It looks to me like you were sent the task (almost) 2 hours after your wingman's 5-day expiration was up. By that time, he had probably started to run it, so his task wasn't cancelled. From there, what TJ said... :-)

If that is the case is some kind of "bug in credit system", if my host receive the WU AFTER the wingman expiration time and process and report it within the 24 hrs is expected my WU receive the "bonus credit", his must receive 0 because it was reported AFTER his expiration time. Anyway Thanks for the help.

---

If that is the case is some kind of "bug in credit system"...

Perhaps...But, I think it's a relatively rare occurrence and there may be perfectly valid reasons why it works like this. Many people have experienced this same issue (including me not too long ago) and it's been discussed in other threads. Who knows if it will ever change? Crunch on! :-)

---

Yeah, it is an old bug. Not easy to fix, apparently.

MrS

---

Scanning for our furry friends since Jan 2002

Thanks all for the answers.

---