Please do not manually report as Richard has stated.
Reporting is automatic when it needs to ask for more work. You may get 2-3 (or more) Ready To Report, and this is actually good for the project. A report is a large hit on the database, because it needs to update several tables. If you report 2 or 3 (or more) the database hit is nearly exactly the same as reporting 1. Saving database hits is important to keep the web pages, project, etc. stable, as it does not over tax the machines.
He's talking about 3rd party core clients that return results immediately, but the same logic applies to hitting the update button to report your results.
Yep, let it do it's own thing. Given that there's always some irreducible/non-scaling overhead in making/breaking a connection for a transaction over the net, then fewer ( but no doubt larger ) 'meals' reduces the overall fraction of time 'dishwashing'. This would be of greater benefit to the server as opposed to a single user, for a given instance, but indirectly it helps all. I have a small farm of 10 hosts at home, plus another three at work, and my 'BOINCView' frequently/easily lists a dozen or more pending reports - more so if I've been doing alot of 'shorts'. They all report in the end, usually/definitely within hours of completion, and I trust whatever algorithm(s) the smart people have come up with to manage that OK. :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Ready to Report
)
Open BOINC Manager, open "Projects" tab, highlite Einstein@Home and click on the "Update" button in the the Commands column.
TTYL
Richard
Please do not manually report
)
Please do not manually report as Richard has stated.
Reporting is automatic when it needs to ask for more work. You may get 2-3 (or more) Ready To Report, and this is actually good for the project. A report is a large hit on the database, because it needs to update several tables. If you report 2 or 3 (or more) the database hit is nearly exactly the same as reporting 1. Saving database hits is important to keep the web pages, project, etc. stable, as it does not over tax the machines.
Slightly related blog entry
)
Slightly related blog entry from Rom Walton.
He's talking about 3rd party core clients that return results immediately, but the same logic applies to hitting the update button to report your results.
Kathryn :o)
Einstein@Home Moderator
Yep, let it do it's own
)
Yep, let it do it's own thing. Given that there's always some irreducible/non-scaling overhead in making/breaking a connection for a transaction over the net, then fewer ( but no doubt larger ) 'meals' reduces the overall fraction of time 'dishwashing'. This would be of greater benefit to the server as opposed to a single user, for a given instance, but indirectly it helps all. I have a small farm of 10 hosts at home, plus another three at work, and my 'BOINCView' frequently/easily lists a dozen or more pending reports - more so if I've been doing alot of 'shorts'. They all report in the end, usually/definitely within hours of completion, and I trust whatever algorithm(s) the smart people have come up with to manage that OK. :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal