The only thing that looks remotely sane to me is having the workunits linked to the amount of work that is requested, i.e. the more work the client requests at once, the more likely it is to be given larger workunits. This should in principle give the larger chunks of work to the faster Apps (in the long term).
Not when the Duration Correction Factor (DCF) is low (mine is something like 0.24 here at Einstein) and the calculated estimate of result lengths done by you (E@H) is 9 hours.
As I see it, only when you disable things left and right, you can do it. But why be looking remotely sane at it, when you're being beat by the applications at this moment?
As far as I see it, BOINC was created as a Distributed Computing platform, so why people are fighting against it and then blaming the project, is anyone's guess. ;)
When they done their work for the day, then that's it.
If their computers fall silent and there's still x hours in the day left, then it isn't E@H's fault, but the end user's fault for ignoring what BOINC was made for.
And as for credits, you may rethink about giving them out. Just to see how many people will still crunch around here, when credits/cobblestones are no longer given out. ;)
I'm rather against fixing something that isn't broken.
I totally agree! The fact is that unforeseen circumstances ( all hail akosf!! ) have pushed some limits of an existing system - which is nice in a way. Even a 150A circuit breaker got the wobbles! Improvement is always possible. But at this point the odds of the bet are the wrong way, as you have to risk $10 in order to win $1.
Quote:
As far as I see it, BOINC was created as a Distributed Computing platform, so why people are fighting against it and then blaming the project, is anyone's guess. ;)
Yeah! The other 'subtle' one is why people are blaming a project for lack of action on various grounds, but forgetting they had volunteered their resources to the project because it didn't have enough! Did anyone close the circle on that one? Sigh.....
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
RE: The only thing that
)
Not when the Duration Correction Factor (DCF) is low (mine is something like 0.24 here at Einstein) and the calculated estimate of result lengths done by you (E@H) is 9 hours.
As I see it, only when you disable things left and right, you can do it. But why be looking remotely sane at it, when you're being beat by the applications at this moment?
As far as I see it, BOINC was created as a Distributed Computing platform, so why people are fighting against it and then blaming the project, is anyone's guess. ;)
When they done their work for the day, then that's it.
If their computers fall silent and there's still x hours in the day left, then it isn't E@H's fault, but the end user's fault for ignoring what BOINC was made for.
And as for credits, you may rethink about giving them out. Just to see how many people will still crunch around here, when credits/cobblestones are no longer given out. ;)
RE: I'm rather against
)
I totally agree! The fact is that unforeseen circumstances ( all hail akosf!! ) have pushed some limits of an existing system - which is nice in a way. Even a 150A circuit breaker got the wobbles! Improvement is always possible. But at this point the odds of the bet are the wrong way, as you have to risk $10 in order to win $1.
Yeah! The other 'subtle' one is why people are blaming a project for lack of action on various grounds, but forgetting they had volunteered their resources to the project because it didn't have enough! Did anyone close the circle on that one? Sigh.....
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