| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Server can't open database. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 26
|
|
| Author |
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: 
|
Lanbrown, what makes you think they wouldn't be privy? Many of the teams participating have members that run WCG regularly. Those people can still choose to bunker and can still load up a rather large cache of re-sends as well. So, not sure if you have thought that through completely....
----------------------------------------    |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
1) They would need to be active members of all projects. If you just run one WCG project, that does not reflect on other WCG projects.
2) It is also machine based and not based on the user. 3) Past history of crunching on other projects besides WCG, when the Pentathlon is run on that project, you have an influx on new members and new machines. 3a) This usually almost always causes issues for the regular crunchers. Last year another project had serious issues coping with the demand and had to turn various tasks off just so they could at least accept and send new WU's. Another project ran into storage limitations in that their storage system was at 100% I/O and was virtually impossible to get any or report any WU's because of it. This started right at Zero hour of the start of the Pentathlon as they were trying to return huge numbers of results. You had users crunching for 10 days before the start so that as soon as the window opened, they could return 10 days worth of units. Hours before they could report, there were a huge number of resends since some units passed the return window. Obviously some started a little before the 10-day mark. 4) There are many BOINC projects and not everyone runs WCG. 5) WCG has had issues in the past when it was just the regulars; being a part of the Pentathlon is just going to cause huge issues like we have seen in the past. I expect to see the storage issue we have seen previously when MCM had very short WU's. The huge influx of returned WU's caused disk space issues and accepting completed WU's was very, very slow and problematic. Care to guess what will happen on May 5th? You know team members have been crunching away ahead of the start so that they can return the results on May 5th and get more. 6) They don't want resends as they would start crunching many days before the start and resends have a short return timeframe. Resends are what they don't want. 7) They would have a long buffer setting which would exclude them from getting resends since by the time they got to the resend, it would have been reissued out. 8) Expect a huge number of resends starting around May 19th. They probably have their buffer set to 10-days and on the 19th when it is over, they will either detach from the project or just let the WU's timeout. Once again, past history. The Pentathlon does very little in terms of helping. Sure there is an increase in WU's returned for a brief period of time, but many people who can't get WU's might find other projects to crunch. Say that there is a 500% increase in returned WU's for two weeks, if you are talking about a project that lasts two or more years, you might have taken 10 weeks off of it. What happens if enough people leave and that 2 years is now 2.5 years. Did the Pentathlon really help? Nope, not at all. Having to resend many, many WU's also causes issues...back to that storage issue. It can't move past the front-end until they are validated and they can't be validated until the quorum is met. Seems you haven't thought that through completely. |
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges:
|
Except that there are many that jump on the bunkering bandwagon even to get just a couple days worth of bunkering in. So, as people get their last minute bunkering fix, they will still suck up even those resend work units pretty quick. Not everyone goes for the full 10 days. Some will keep it small like the 4 days so that their machines still qualify for quick returns in the event that BETA work goes out and also means when they get the resends they will validate almost immediately. I'm no stranger to the tactics these teams use. With that knowledge you need to understand that it does not blanket statement exclude them or make them "not privy". That was my point. So, as you described, the bunkering probably drained it quite a bit and put stress on the servers. Then the continued bunkering in conjunction with normal users sucked up even more. Then you have the people that are new that were trying to get what little non-resend work that was still trickling for a bit trying to get their systems some work that might validate during the challenge. So, regardless how you slice it, I don't think WCG expected this hammering. And I have no idea if they were actually given any notice in advance. Which by now really should be common practice and courtesy before anyone issues a challenge. If they did, then who know what is up. We haven't heard much from WCG staff.
----------------------------------------I didn't encourage the behavior to begin with. This wasn't about whether the challenge is positive or negative. This wasn't about whether bunkering is a good or bad thing. This was merely an explanation for what was likely happening and a further explanation as to why your blanket statement had a flaw. Edits: grammatical errors [Edit 2 times, last edit by Coleslaw at May 4, 2015 4:56:38 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I will vote to lanbrown +1. Because it lasts may 5th to 19th, I supporse the unstabilised state will continue to the end of the month. It will not be welcomed by the ordinal crunchers like me.
In any way, I understood this no-work situation will last for a couple of days and there is nothing to do to avoid the situation for me. So I will spend cominng no-work period for the time consuming machine maintenance such as memory installation, cleaning the CPU coolers or may be a good chance for operating system upgrade. Kiyo. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Gone form bad too worse now, geez not a good look at all.
----------------------------------------It dosen't look like new users, have a look at the third graph here. http://boincstats.com/en/stats/15/project/detail/user [Edit 4 times, last edit by Former Member at May 4, 2015 6:53:53 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Except that there are many that jump on the bunkering bandwagon even to get just a couple days worth of bunkering in. So, as people get their last minute bunkering fix, they will still suck up even those resend work units pretty quick. Not everyone goes for the full 10 days. Four days won't get you true resends though; by the time you start crunching them, the due date has been passed. Even if four days did allow them, given that they won't return any results until May 5th, the return date would have been far past. For MCM, if it is a recent resend but not past quorum 2, then it gets the normal 7-day period. If it is an older WU or past a quorum of 3, it is 2.5 days. Setting a four day buffer will not get you resends except for recent ones, not ones that have timed out. In the competition, the name of the game is to do as much work as possible, so they would be set to the max...other teams will. |
||
|
|
|