| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: New Set of Beta WU's - FAAH |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 484
|
|
| Author |
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
08/07/2011 22:42:30 World Community Grid Message from server: Beta - The Clean Energy Project - Phase 2 requires 96.00 kbps download bandwidth. Your computer has been measured at 58.24 kbps
 It's a 16Mbps line. Measured at which end? |
||
|
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges:
|
As soon as I realised a flood was starting, I threw caution to the wind and redeployed my beta-profile net into the waters.
----------------------------------------I have grabbed 30 faah and cep betas   Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
Way to go, coolstream!
----------------------------------------I will finally hit Silver with the next statistics update.  And I've started pulling in WUs from the new batch. |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
08/07/2011 22:42:30 World Community Grid Message from server: Beta - The Clean Energy Project - Phase 2 requires 96.00 kbps download bandwidth. Your computer has been measured at 58.24 kbps It's a 16Mbps line. Measured at which end? Net transfer speed. In this case, I'm sure it is our servers. |
||
|
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges:
|
Thanks, kateiacy. It looks as if the river has run dry again.
----------------------------------------I see that these new betas have a 4-day deadline Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
We appreciate the stress testing that you all have been helping us with. We are currently experiencing a peak bandwidth of about 130Mbps for these servers which is not sufficient to meet the peak demand. We are working to figure out how to increase that.
|
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 3010 Status: Offline Project Badges:
|
We appreciate the stress testing that you all have been helping us with. We are currently experiencing a peak bandwidth of about 130Mbps for these servers which is not sufficient to meet the peak demand. We are working to figure out how to increase that. No worries knreed - we're always keen and willing to help whenever any Beta testing is required  Just keep them coming  |
||
|
|
mfbabb2
Senior Cruncher USA Joined: Feb 18, 2011 Post Count: 361 Status: Offline Project Badges: 
|
We appreciate the stress testing that you all have been helping us with. We are currently experiencing a peak bandwidth of about 130Mbps for these servers which is not sufficient to meet the peak demand. We are working to figure out how to increase that. Would it help to limit to 1 or 2 per CPU request for the big stuff? Or would that just delay the pain?
Murphy
---------------------------------------- [Edit 1 times, last edit by mfbabb2 at Jul 8, 2011 11:06:34 PM] |
||
|
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: 
|
We appreciate the stress testing that you all have been helping us with. We are currently experiencing a peak bandwidth of about 130Mbps for these servers which is not sufficient to meet the peak demand. We are working to figure out how to increase that. Knreed, do you guys really need to increase the bandwidth? I mean, I understand that it didn't meet the peak demand for this beta test, but your bandwidth seems to be fine, I mean CEP2 and all of the other projects have been running fine. So unless this server is using a separate boardband, then it should be ok. Well, you guys are the expert and probably know of some stuff that we are missing. Last piece of note, it is the weekend, go home forget about this. I may have to work this weekend, but you don't  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
On changing profiles. If you change to Beta tasks only, and there are none, after a while Boinc will backoff for 24h. Even if you change the profile online to run all tasks, Boinc will sit and wait 24h unless you do a manual update. For this reason it's wise to only man manage local systems. From an earlier post, I fully agree that a 24h backoff is too long. The WCG has probably never been down for 24h. How much effort is it for a computer to try to connect to the server every 4h at most? It's not like it will eat up all your bandwidth. Could the WCG version of Boinc be configured to have a more sensible setting of say 4h max? Well, BOINC includes 3 different kinds of backoffs, these are: 1: Client can't connect at all. 2: Client connects, but gets a server-deferral. 3: Client connects, but project doesn't have any work available. For #2, in case client connects, but project is shut-down, or can't open database or similar, you'll get a 1-hour deferral. Not sure if these is still included, but some things like "too old BOINC-client", "Unsupported OS or CPU" and so on atleast before immediately gave a 24-hour deferral. Also, since WCG runs very old server-code, you'll still get the quota-deferral until midnight server-time + randomly 1 hour. Lastly, there's also the limits on how fast you can do next connection (currently 10 seconds for WCG) and also an order to client to re-connect in 3 days. For #1, a quick try with v6.12.33 reveals this gives a deferral between 1 minute and 4 hours, as it's always have given. Also, after 10 failed connections in a row, it's reset to 1 minute, but also tries to download the home-page. Very surprisingly, failing to download home-page gave not a 24-hour deferral that was common with earlier clients, so it actually looks like client nows tries more frequent in case of connection-errors than before... #3 starts with a deferral-interval of 10 minutes, and this is doubled upto 24 hours for each consecutive "no work available" from project. The deferral-interval is reset each time a task for project is finished. Since the deferral-interval is reset for each finished task, this means for WCG you'll only hit 24 hours if you've completely out of WCG-work, and you've example choosen to only download DDDT2 or something. Since AFAIK it's over 1 month since last time there was any DDDT2-work, and 1 week since there was any WCG-beta-work available, anyone running wich such WCG-preferences would obviously be out of WCG-work by now. I can't really see how a few people intentionally choosing only to run WCG-projects there it can be over a month between available work should warrant any changes to BOINC's client-behavour...  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|