Forum > GPU crunching
CPU <-> GPU rebranding
Richard Haselgrove:
The problem is, so far as I can tell and contrary to speculation last time we went round this circle. the BOINC doesn't read the cleint_state.xml file back again after writing it.
So you can make any changes you want, and it won't make the slightest difference.
The whole purpose behind the BOINC closedown/restart is to make it READ client_state.xml, and see your changes - and that only happens once, at startup.
Raistmer:
Ah... good point. That is, it will survive w/o access state file but will be shocked by amnesia w/o restart ;D
BUT, there is option in menu for new BOINC clients - re-read state file or smth like this. I know it works for cc_config.xml.
Does it expand on client_state.xml file or not ?
Richard Haselgrove:
No, the only 'read' options are for cc_config.xml and the preferences override file. I very much doubt there will ever be a 're-read' option for the current client_state.xml file, because it changes so darn quickly: if you read it back, all the progress %ages would drop back 5 seconds or whatever. For the moment, I think the only safe thing to do is to treat client_state.xml as read-only while BOINC is running, and only make modifications after the client has fully shut down - that way, all the latest state info will have been flushed to disk and the source for the modifications will be reliable.
In the longer term (but certainly not in any of the BOINC v6.6 range), they've realised that re-writing a statefile with thousands of 'waiting to run' entries every few seconds is very wasteful. There's talk of separating out the fast-changing stuff about active tasks in progress into a much smaller file: the main cache file would then change much more slowly (perhaps only when the client contacts a server, or one task finishes and another starts). It might be possible to modify and read back the cache file then, but it still feels risky to me, and I doubt the developers would include code for it just to accommodate this script. So Lunatics would have to write a modified BOINC core client with read capability.....
..... except that by then, it won't be needed, of course. By then, Raistmer will have solved the VLAR problem and stock crunchers will be using CUDA cards for all MB work, and the Lunatics will be using CUDA for the AP jobs where it really belongs ;D
@ Marius: yes, I think the jobs are listed in client_state in the order they're assigned by the server (i.e. the order you see them in BOINC Manager if you don't have any column sorting in operation)
@ everybody else: 16 downloads already - we have a lot of budding developers lurking silently in our midst :o But remember, the instructions are in Fred's file, and you will get NO SUPPORT unless you contribute to the development effort.
Raistmer:
;D ;D ;D
Claggy:
--- Quote from: Richard Haselgrove on 03 Jun 2009, 04:58:36 am ---
@ everybody else: 16 downloads already - we have a lot of budding developers lurking silently in our midst :o But remember, the instructions are in Fred's file, and you will get NO SUPPORT unless you contribute to the development effort.
--- End quote ---
Sorry, but at least 10 of those were me attempting to get Getright to download it, and failing, shut down Getright then got it first time, :-[
not tried it yet as have no fresh Cuda tasks (PC isn't net connected at the moment)
Claggy
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version