OK...how did THIS timeout happen? |
![]() |
| log in |
Message boards : Number crunching : OK...how did THIS timeout happen?
| Author | Message |
|---|---|
|
AP WU 1142265986. | |
| ID: 1321095 · | |
|
I've always thought that it was part of the same mechanism that stops VLAR's being sent on a nVIDIA request myself. | |
| ID: 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 · | |
|
Got another one just about like it.......must be the idiot scheduler sending WUs where they don't belong because comms are trashed. | |
| ID: 1321120 · | |
I've always thought that it was part of the same mechanism that stops VLAR's being sent on a nVIDIA request myself. 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 · | |
Message boards : Number crunching : OK...how did THIS timeout happen?
| Copyright © 2013 University of California |