... any worries about server overload then, were completely dismissed just recently as we transitioned.
I don't think user concerns are ever just "dismissed" out of hand. I like to think of it more as "still trying to work out exactly what happened, and why, and if it can be mitigated against in future ..." rather than "stuff the users, they don't need to know" :). I'm sure, in the fullness of time, we'll get a summary of what actually happened and why.
I imagine that David Hammer is doing the bulk of the recovery work and with Bruce moving himself and family to Germany, about the time of that horrendous storm across Europe, I'm not surprised that there has been a lack of hard information. People will speculate, so that tends to make things look worse then they perhaps are.
As far as I'm concerned, the most important thing is that the project seems to have stabilised and with the minor delays and mini-outages that are occasionally happening, there must be fixes being tested and implemented behind the scenes. I'm back to not having to even look at machines for days on end so I'm happy.
Quote:
"Remember December?" What fun.
You have a way with words sir!! You are hereby appointed as the official namer of EAH significant events!! :).
Quote:
Warmest Regards-tweakster
And to you too!! I really am very pleased to see your growing credit contribution on this project again.
What I couldn't understand about the "Curse of 32" was the point that even though computers that were using Akos' apps and hitting the 32 daily limit, those boxes were getting more credit overall then they would've before received w/o the supercharged apps and not hitting the 32 ceiling. Or am I wrong in this assumption?
... those boxes were getting more credit overall ...
Yes, that is true and easily understood if you remember the size of the quorum and how credit was calculated in those days. As a simple example, remember that the credit claim was based on both benchmarks and crunch time. So if your crunch time was 5 times faster using the optimised app you would only claim 1/5 of what you would have claimed with the standard app, if the benchmarks were unchanged. However, if your quorum partners were both claiming the standard amount, you can guess what is going to happen with your very low claim most of the time.
Another trick used was to look for an optimised boinc client to boost your benchmarks. That way you would be claiming closer to what the standard app was claiming but finishing 5 times as much work. Even if you were only working for 12 hours, you would still be finishing 2.5 times more work than what the standard apps were producing.
Thankfully, with server determined credit, all this is dead and buried in the distant past and should be left there.
That is great, but it would be even greater if the graphs at homepage.hispeed.ch/einstein revived. Anyone know the owner? Or does that rely on something from Einstein which has not been restarted?
After 28 days the E@H Server Status Site is back online ! Congratulation to the people , who run the servers. I think, they do a good, stressing job.
But still I believe, more infomation about the situation would be fair in regard to the people behind the computers all over the world. This can be done without unacceptable more workload. The hosts don´t require this information indeed, but the people behind them are humans, and they like to take in some way part in what is going on.
In the near past there have been several remarks in this forum with the same tenor.
RE: ... any worries about
)
I don't think user concerns are ever just "dismissed" out of hand. I like to think of it more as "still trying to work out exactly what happened, and why, and if it can be mitigated against in future ..." rather than "stuff the users, they don't need to know" :). I'm sure, in the fullness of time, we'll get a summary of what actually happened and why.
I imagine that David Hammer is doing the bulk of the recovery work and with Bruce moving himself and family to Germany, about the time of that horrendous storm across Europe, I'm not surprised that there has been a lack of hard information. People will speculate, so that tends to make things look worse then they perhaps are.
As far as I'm concerned, the most important thing is that the project seems to have stabilised and with the minor delays and mini-outages that are occasionally happening, there must be fixes being tested and implemented behind the scenes. I'm back to not having to even look at machines for days on end so I'm happy.
You have a way with words sir!! You are hereby appointed as the official namer of EAH significant events!! :).
And to you too!! I really am very pleased to see your growing credit contribution on this project again.
Cheers,
Gary.
What I couldn't understand
)
What I couldn't understand about the "Curse of 32" was the point that even though computers that were using Akos' apps and hitting the 32 daily limit, those boxes were getting more credit overall then they would've before received w/o the supercharged apps and not hitting the 32 ceiling. Or am I wrong in this assumption?
RE: ... those boxes were
)
Yes, that is true and easily understood if you remember the size of the quorum and how credit was calculated in those days. As a simple example, remember that the credit claim was based on both benchmarks and crunch time. So if your crunch time was 5 times faster using the optimised app you would only claim 1/5 of what you would have claimed with the standard app, if the benchmarks were unchanged. However, if your quorum partners were both claiming the standard amount, you can guess what is going to happen with your very low claim most of the time.
Another trick used was to look for an optimised boinc client to boost your benchmarks. That way you would be claiming closer to what the standard app was claiming but finishing 5 times as much work. Even if you were only working for 12 hours, you would still be finishing 2.5 times more work than what the standard apps were producing.
Thankfully, with server determined credit, all this is dead and buried in the distant past and should be left there.
Cheers,
Gary.
RE: Thankfully, with server
)
I absolutely agree with you.
I figured that since this thread was turning into a memory lane of sorts, I'd scrape some of the mud off my boots :P
RE: That is great, but it
)
I've restarted the graph this evening.
regards
RE: I've restarted the
)
Much thanks. I love your graphs, by the way.
RE: After 28 days the E@H
)
Hi Martin,
could you please post the link?
Thanks!
Hate to say this but at
)
Hate to say this but at moment it appears to be down again.
Andy
Validator seems to be down
)
Validator seems to be down too or needs a good kick to get it get it to move faster. Maybe they need to hire sombody with a bigger whip , lol.
98SE XP2500+ @ 2.1 GHz Boinc v5.8.8
