OK...how did THIS timeout happen?


Advanced search

Message boards : Number crunching : OK...how did THIS timeout happen?
Message board moderation

To post messages, you must log in.

AuthorMessage
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1321095 - Posted: 29 Dec 2012, 2:38:24 UTC

AP WU 1142265986.
Sent to one of my rig and one other on 28 Dec 2012 | 22:23:40 UTC.

The other user has a deadline of 22 Jan 2013 | 22:23:40 UTC.
Mine shows time out, no response at 29 Dec 2012 | 2:28:26 UTC.
It was then reissued with a deadline of 23 Jan 2013 | 2:28:37 UTC.

Why didn't the kitties have until Jan. 22nd to finish it?
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1321095 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 34744
Credit: 261,360,520
RAC: 489
Australia
Message 1321099 - Posted: 29 Dec 2012, 2:44:29 UTC - in response to Message 1321095.  

I've always thought that it was part of the same mechanism that stops VLAR's being sent on a nVIDIA request myself.

Cheers.
ID: 1321099 · Report as offensive
Cruncher-American Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor

Send message
Joined: 25 Mar 02
Posts: 1513
Credit: 370,893,186
RAC: 340
United States
Message 1321106 - Posted: 29 Dec 2012, 3:38:52 UTC - in response to Message 1321099.  

I've always thought that it was part of the same mechanism that stops VLAR's being sent on a nVIDIA request myself.


Could you please explain this remark? Is it a joke? Am I missing something (besides 100 or so IQ points)?
ID: 1321106 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1321120 - Posted: 29 Dec 2012, 4:30:15 UTC

Got another one just about like it.......must be the idiot scheduler sending WUs where they don't belong because comms are trashed.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1321120 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 34744
Credit: 261,360,520
RAC: 489
Australia
Message 1321145 - Posted: 29 Dec 2012, 5:49:55 UTC - in response to Message 1321106.  

I've always thought that it was part of the same mechanism that stops VLAR's being sent on a nVIDIA request myself.


Could you please explain this remark? Is it a joke? Am I missing something (besides 100 or so IQ points)?

With people who are not running the nVIDIA openCL app then the Astropulse workunit will be treated the same as a VLAR, CPU request makes it through but isn't acknowledged at the user end so the workunit becomes a ghost and then the machine requests GPU work so any ghosts that can only run on CPU for that setup will be automatically timed out.

Cheers.
ID: 1321145 · Report as offensive

Message boards : Number crunching : OK...how did THIS timeout happen?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.