| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Enhanced BOINC from truXoft |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is anybody else using the enhanced BOINC from http://boinc.truxoft.com, referred to as Truxoft BOINC? I use it and it works well for me.
The official BOINC is open source. Truxoft has made a few modifications aimed primarily for those crunching for SETI project. However, Truxoft BOINC has one nice feature that is good for WCG too. Truxoft BOINC can be configured to return WU results immediately. Official BOINC waits a long time to report results back to the project. I would think reporting results immediately upon completion of the WU is a good thing for all concerned. Configuring Truxoft BOINC is fairly easy but there is 1 small "bug" I would like to mention. Truxoft BOINC comes with the "return results immediately" option turned OFF. You must turn the option ON manually if you want to use it. To turn it ON you must add the following line to the truxoft_prefs.xml file: <return_results_immediately/> The file should then look like: <truXoft_conf> <return_results_immediately/> </truXoft_conf> The bug is that the <return_results_immediately/> must be the first item in the list of options else it gets ignored and that option does not turn ON. If you do not crunch SETI@home WUs then the other options are of no use to you. In that case it's probably best to edit the truxoft_prefs.xml file to look exactly like the above example. BOINC will tell you whether or not it is configured properly to return results immediately. If you look at the Messages page in BOINC it will report: truXoft addon: return_results_immediately. If it does not show the above line then try restarting BOINC and/or check for spelling/syntax errors in the truxoft_prefs.xml file. -- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think (I could be wrong) that this is also being added to the official client. It hasn't made it to the stable branch yet, though.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think (I could be wrong) that this is also being added to the official client. It hasn't made it to the stable branch yet, though. That would be good news. I look forward to the stable version. -- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think (I could be wrong) that this is also being added to the official client. It hasn't made it to the stable branch yet, though. Yes you are wrong on that one  BOINC does not return results imediatly on the next version due out, it will act as normal in a 2 stage process. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
They have added a command line option: -return_results_immediately
It was added in version 5.1.2, but it doesn't appear to do anything (nothing good, anyway). |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The return results immediately flag was for initial testing and was supposed to be removed by version 3.xx. Due to a compiling error it was the default behavior in the 4.45 release client. Since this was the recommended client for a fairly long period many participants thought this was the desired behavior, however it is a bug.
The reintroduction of this bug in the trux client is the only reason I do not recommend that client, in all other ways the trux client is an order of magnitude better than any other optimised client. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Bug? It's only an option in the truXoft version, not the default.
Although it does seem to be all very, very confused. If the flag was there originally, why was it added in 5.1.2? Why doesn't it work properly in 5.2.13? Why was it the default in 4.45? Why indeed! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
if i am online i tend to push the "update" button to get results sent but my linux box is not connected to monitor so i just set and forget, the amd dual core linux moves along very fast so 5-6hrs for a w/u is prob not a big deal time wise, the HT pentiums take about 11hrs per HyperThreaded work/unit so i tendt to send if i note the reluts are "parked" cheers..
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Bug? It's only an option in the truXoft version, not the default. Although it does seem to be all very, very confused. If the flag was there originally, why was it added in 5.1.2? Why doesn't it work properly in 5.2.13? Why was it the default in 4.45? Why indeed! LOL! Good questions, all of them! I'll add it to my list of things that drive the code cutters nuts and not mention it again. -- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Bug? It's only an option in the truXoft version, not the default. Although it does seem to be all very, very confused. If the flag was there originally, why was it added in 5.1.2? Why doesn't it work properly in 5.2.13? Why was it the default in 4.45? Why indeed! LOL! Good questions, all of them! I'll add it to my list of things that drive the code cutters nuts and not mention it again. -- It was finally removed about 5.1.2, actually a few revs earlier if I remember correctly, but that was the first one to stay on the download page for any length of time after. That is also why it does not work in any later version. A compile bug caused it to be the default in 4.45. |
||
|
|
|