LHC@home

Hi all,

The Upload process is a 2 part step.
First the completed Work Units are uploaded,as soon as they are finished calculating.

Later the now turned into ready to Report, is to be uploaded.

This upload of the rRep is done by user (update) or
by the client, when the client is connecting the scheduler next time.


So now, my curiosity driven question:

what are YOU doing with the ready to Report?

-are you doing yourself from time2time an "update"?

-are you letting the client making the choise?

-are you using a combination of let the client do and doing yourself the update?

Any posting is welcomed and sayed thankyou for it.


Myself giving from time to time a "update", I have seen, in "my" environment,
the rRep are going "slowly" away. Until they go away, the next generation of rRep is created.

Having 30-50 rRep, all the time, it's not unusual, specially with the short running work.

friendly

ric



multi Project BOINC Stats
Team
Individual

I never have more than 1 or 2, but than again I am running 4.52 CC ;o)Oppps I let BOINC do it........

I doing self push 2 times the update buttom.

me too



Greetings from Germany
Basti

Same here, every morning, my BOINCview monitoring 10 Hosts (12 active CPU's) is full of those.

Since I like things "clean" I update them all, and this in turn makes other crunchers happy because the Results are verified quicker that way :)
___________________________________________
<p>Scientific Network : 36200 MHz �� 8204 MB �� 815.0 GB </p>

I have a .1 day queue, 8 projects and 10 machines. I let BOINC do it.

I manually update if I see something ready to report, but there are times where I won't see a cruncher for a week so it's kind of both for me.
---

Generally, I manually update if I see six or eight (or more) results sitting with a "Ready to report" status. Rarely do I let BOINC do it.

By doing it manually, I get the results reported so they're not setting on my machine, and other people can get their credits sooner.

Cheers,

Stephen
<a> [/url]

I usually let the client do it's own thing -- it's no hassle to let it just sit there. =D It's not the fastest way of giving the validator results, but it's the intended mode (and will be the mode used by people who aren't as "into" BOINC as some of us.

Sometimes I'll use the "-return_results_immediately" switch on BOINC which forces it to talk to the scheduler after it uploads (essentially the same as hitting update as soon as a WU finishes), but with BOINC being updated so often I haven't remembered to add the switch in the shortcut ^_^;;;;


[url=//spreadfirefox.com/community/?q=affiliates&id=1015&t=85]

@Puffy I'll use the "-return_results_immediately" switch on BOINC
============

Where do I put this switch in the shortcut Puffy ... ???

JOIN THE LHC@HOME TEAM

>
> Where do I put this switch in the shortcut Puffy ... ???

Perhaps wrong.
This parameter is only valid for the Command line interface (running as a service, or in a CMD), NOT for the GUI

Installing and running the BOINC command-line client

> Perhaps wrong.
> This parameter is only valid for the Command line interface (running as a
> service, or in a CMD), NOT for the GUI
>

With 4.13 on windows this switch also works for the gui ;)



greetz, Uli

I do a mix. Generally, I let BOINC update on its own schedule. However, since my machines are not (and cannot) be on 24/7, I also update manually sometimes (especially near the end of the work day).

I'd also point out that updating is not just for reporting uploaded work units. I will occaisionally do an update so that the project totals are current (rather than having to visit the websites of all 5 projects to which I am attached).

I just let BOINC manage it all.

BOINC has the ability to be almost completely self-sustaining.

I fully intend to let BOINC decide what it wants to do. This doesn't always happen, for various reasons. Often my own impatience or because due date is close or because I fiddled with preferences.
I'm embarrassed to admit that I�ve manually updated to get a result reported before another user on a few occasions.
In the future I can see leaving BOINC unattended for longer periods.

ric yes
Pascal K, G no
Welcome at the Cold War yes
Basti yes
FalconFly yes
John McLeod VII no
tiker yes
Stephen Balch yes
Puffy (yes) if he could, he would?
Scott Brown yes
Trane Francks no
Contact yes

Total "valid" 12

the No 3 (25%)
the Yes 9 (75%)

A very warm thankyou for sharing this information.

It's not representative but offers a view NOW.
Both is valid the same way.

I don't now why, but I have the feeling, saying yes I do "update" has still a kind of "negative touch". If there is a bottom/function, why don't we should use it.
As far as I undestood, the reason why the finished work upload and rRep "upload" is not done the the same step, is to not overload the server(s)

While doing the "update"(-to the project), the project preferences, user/host information and other are updated. Scott putted it out well, some of the updated informations are the host and total credit(RAC) shown in the GUI


"-return_results_immediately" switch
My very personal tests and experiments on july turn into no using this parameter.
All 3 tested boinc monitoring/management programms/addons public available

having problems to recognize the finishes state and therefore loosing stats-information (sometimes not in log).
As more clients are running, as more the monitoring tool takes time to get the states from every client in time. with "-return.." this time is to reduced
And it's a one time "try to send".

once more time, thankyou for giving an insight into

perhaps one day, we don't have to "project-updade", it's doing itself...

let's dream.

Have a goot time till the project will temporary offlined

kind regards

ric

I report manually every time I see a Ready to Report unit waiting :-)

>
> It's not representative but offers a view NOW.
> Both is valid the same way.
>

Actually, it is representative... of a very small number of users, of only those who use the Fora, and who read your message, and who bothered to reply (GRIN).

I agree, both methods are equally valid. I do it the way I do because it gets results to LHC faster than waiting for BOINC to do it, and other users, many of whom complain bitterly if they don't get credits quickly, can get their results validated faster and get their credits faster.

Cheers,

Stephen
<a> [/url]