If you got an HT enabled cpu and taking part in at least one other project (let's say Seti@Home) than EaH, you can speed up crunching time by using this line in your truxoft_prefs.xml
Einstein@Home,SETI@Home
That way you crunch Einstein on one (logical) cpu and seti on the other. Due to different overheads the cashes are used in a much more efficient way and the crunching time decreases again... ;-)
AndyK
I've been wanting to do this. Does this line require modification for enhanced SETI? If so do you know the new string?
I've been wanting to do this. Does this line require modification for enhanced SETI? If so do you know the new string?
I'm going to guess that the prefs file compares the present strings to those you see in BOINC Manager under the Projects tab and project heading. As long as those two match, it should be fine.
I've been wanting to do this. Does this line require modification for enhanced SETI? If so do you know the new string?
I'm going to guess that the prefs file compares the present strings to those you see in BOINC Manager under the Projects tab and project heading. As long as those two match, it should be fine.
After one night's experience running both enhanced an non-enhanced, it appears you are right. Thanks.
Wasn't part of my training 36 years ago. Did they even run on IBM 360/20? lol
Sorry, folks, but I let it all drop, and at the wrong time. What a waste!
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Compatibility: all truXoft releases
Scope: global, project, schedule
Example:
This option forces the BOINC client to report completed results immediately after uploading the result. Please note that the immediate reporting of the result may fail in some cases - for example when the network connection is not available, when the server is down or refuses the request, when another scheduler request has been made shortly before the current one, and possibly in some other situations. The WU will be then reported at the next scheduled time, or at the completion of the next WU (whatever comes first). Depending on the availability of the project server, the failure rate is typically around 10%.
Copied from website. Hope this is what you was wanting. gl
This option forces the BOINC client to report completed results immediately after uploading the result.
gl
One caution. If you use this option and are a BOINCView user, the rapid result reporting may cause many of your results to escape BOINCView's notice, so not appearing in the completed work list.
This at least was my experience, which was doubtless partly affected by my choice to run BOINCView update interval at 1 or two minutes rather than a few seconds in order to decrease its very considerable CPU overhead when opened for view.
This option forces the BOINC client to report completed results immediately after uploading the result.
gl
One caution. If you use this option and are a BOINCView user, the rapid result reporting may cause many of your results to escape BOINCView's notice, so not appearing in the completed work list.
This at least was my experience, which was doubtless partly affected by my choice to run BOINCView update interval at 1 or two minutes rather than a few seconds in order to decrease its very considerable CPU overhead when opened for view.
archae86,
Thank you. Is it just that one simple line I have to add? I am not using BoincView, btw.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
One caution. If you use this option and are a BOINCView user, the rapid result reporting may cause many of your results to escape BOINCView's notice, so not appearing in the completed work list.
Is it just that one simple line I have to add? I am not using BoincView, btw.
Yes, just the one line in the body. Aside from the BoincView impact, and a bit more communication load on the project's servers, I don't know of adverse impact.
RE: If you got an HT
)
I've been wanting to do this. Does this line require modification for enhanced SETI? If so do you know the new string?
Thanks.
RE: I've been wanting to do
)
I'm going to guess that the prefs file compares the present strings to those you see in BOINC Manager under the Projects tab and project heading. As long as those two match, it should be fine.
RE: RE: I've been wanting
)
After one night's experience running both enhanced an non-enhanced, it appears you are right. Thanks.
Hello, All, Could someone
)
Hello, All,
Could someone please give me the code line to force report results immediately?
My coding days are long behind me, as in RPG (NOT RPG2), COBOL, FORTRAN IV,etc. :-{ hehe. We're talking ancient here.
Michael R.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: We're talking ancient
)
How about BASIC or Logo? lol
RE: RE: We're talking
)
Wasn't part of my training 36 years ago. Did they even run on IBM 360/20? lol
Sorry, folks, but I let it all drop, and at the wrong time. What a waste!
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Compatibility: all truXoft
)
Compatibility: all truXoft releases
Scope: global, project, schedule
Example:
This option forces the BOINC client to report completed results immediately after uploading the result. Please note that the immediate reporting of the result may fail in some cases - for example when the network connection is not available, when the server is down or refuses the request, when another scheduler request has been made shortly before the current one, and possibly in some other situations. The WU will be then reported at the next scheduled time, or at the completion of the next WU (whatever comes first). Depending on the availability of the project server, the failure rate is typically around 10%.
Copied from website. Hope this is what you was wanting. gl
RE: Example: This option
)
One caution. If you use this option and are a BOINCView user, the rapid result reporting may cause many of your results to escape BOINCView's notice, so not appearing in the completed work list.
This at least was my experience, which was doubtless partly affected by my choice to run BOINCView update interval at 1 or two minutes rather than a few seconds in order to decrease its very considerable CPU overhead when opened for view.
RE: RE: Example: This
)
archae86,
Thank you. Is it just that one simple line I have to add? I am not using BoincView, btw.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: RE: RE: One
)
Yes, just the one line in the body. Aside from the BoincView impact, and a bit more communication load on the project's servers, I don't know of adverse impact.