OK...how did THIS timeout happen?


log in

Advanced search

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

Author Message
Profile Wiggo
Avatar
Send message
Joined: 24 Jan 00
Posts: 7331
Credit: 96,803,683
RAC: 67,128
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.
____________

jravin
Send message
Joined: 25 Mar 02
Posts: 941
Credit: 102,410,888
RAC: 88,121
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)?

____________

Profile Wiggo
Avatar
Send message
Joined: 24 Jan 00
Posts: 7331
Credit: 96,803,683
RAC: 67,128
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.
____________

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

Copyright © 2014 University of California