Busy Bytes (Jul 06 2009) |
![]() |
| log in |
Message boards : Technical News : Busy Bytes (Jul 06 2009)
Previous · 1 · 2 · 3 · 4 · 5 · Next
| Author | Message |
|---|---|
|
There is no "prize" at the end of a fictitious line here, so if there is down time, people should understand that, take a deep breath and wait for it to clear. Being #1 cruncher gets you what, bragging rights on a message board!? Matt is in the most awful position here by having to obey orders, even if he disagrees, or has better ideas that are falling on def ears. It would be great for another 80k, but with today's financial rout, that will be just as hard as have a problem free seti@home day. BTW, I'll be in the top 50 of my class tomorrow, first milestone! | |
| ID: 915168 · | |
wrong answer the problem onley started within the last three weeks.... before not to bad ... something changed but what?????????????????? CUDA No Seriously! A lot of people have gone out a gotten a card to crunch more. It takes just one straw to break the camels back. Someone bought that card and put it up. Too much of a good thing ... If everyone took 5% off their SETI percentage and gave it to their backup project(s) it would clear the logjam for now. The long term answer is $$$ to get gigabit up the hill. I've got an alternative suggestion for those that refuse to run a backup. Turn your computer off for an hour or two a day and send the $$ you don't spend on electricity in as a donation. ____________ | |
| ID: 915169 · | |
Re: Maxed out Bandwidth. I made more or less the same suggestion in another thread. However, I thought that if they could prioritize the uploads, without a static restriction, that would help solve the problem. Nobody seemed to understand my suggestion, or it is a bad one. I don't think reducing cache size matters too much, but reducing storage requirements by being sure the uploads succeed does make sense, even at the inefficient use of bandwidth. A while ago, seti was running on 1/2 the band width and pegging it. Something happened and the bandwidth doubled, and overnight it was pegged again. Since the number of users didn't change so quickly, and this was before the baraCUDA, I think procedure in the back-office must have changed to choke the bandwidth chicken. From a different perspective, like any other 'free' resource, bandwidth will be used until it is used up. The fact that the bandwidth use is pegged so frequently is no surprise. However, the boinc system (including mysql) just doesn't seem to be very solid or at least doesn't seem optimized. I'd rather see some change in procedures or evolution of boinc, before investing in yet more hardware and the like. It's a matter of trust, I suppose. | |
| ID: 915171 · | |
wrong answer the problem onley started within the last three weeks.... before not to bad ... something changed but what?????????????????? If you think it's never happened before, then you've not noticed, or you've forgotten. The problem starts when there is some sort of interruption -- a server fails, or some bottleneck slows things down, and it doesn't get caught right away. Over the next day or so, a backlog builds up, and then the BOINC clients start trying to "push through" all at once. It's particularly bad when there is a batch of "short" work like we've had lately, because that also increases the load. The glitch that over-distributed Astropulse adds to that, since AP work units are long. Faster processors (and CUDA) increase load as well, but that didn't happen in the last three weeks. In other words, several things have pushed the load just a little beyond "normal" and it doesn't take much. But it has all happened before, and at least so far it doesn't seem any worse than earlier glitches. ____________ | |
| ID: 915207 · | |
|
Are there any "spare" servers, down the hill or elsewhere on/off campus, belonging to the Space Sciences Lab that could be used as a download mirror for data distribution to clients, to relieve pressure on the normal servers? | |
| ID: 915249 · | |
|
I was just about to suggest using mirrors. Looks like Einstein@Home use them. | |
| ID: 915253 · | |
|
| |
| ID: 915256 · | |
|
| |
| ID: 915257 · | |
It's not possible to make it wireless? It is. ____________ Grant Darwin NT. | |
| ID: 915259 · | |
It's not possible to make it wireless? And.. why they don't do it? ;-) I guess it would be a lot cheaper than with cable.. Maybe here are people around which have knowledge about wireless equipment (WLAN, SAT, radio, or what ever) and knowledge how to do it? ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 915270 · | |
|
An other idea.. (maybe) ___>=__ ___<___ _id's_ active % ______0 _500000 152071 45589 30 _500000 2500000 132865 25980 20 2500000 8250000 170345 20092 12 8250000 8500000 154294 14652 _9 8500000 8750000 155417 12821 _8 8750000 9000000 164536 20945 13 9000000 9999999 _59176 24888 42 and for the 'read queries' use a MRG_MyISAM structure.. that way I could write to the needed table based upon an id 'greater then .. AND less then ..' and keep the reading simple with the merge table. This might help in: - easier backup and restore (less massive backup files, partial restores if needed) - less fragmentation due to smaller tables => more stability - faster due to smaller index tables => more stability The potential unhandy part is that I discovered that altered data in the underlying table isn't pushed to the merge-table. In an other table structure I used this to fix that: ALTER TABLE `merge_table` UNION=(`table_1`,`table_2`....); I haven't done any testing what this query does on a huge table... (it worked like a charm on a couple of 50k rows tables though :D) Is there merit to this idea and could "table splitting" be an idea for the Berkeley tables as well? ____________ The SETI@Home Gauntlet 2012 april 16 - 30| info / chat | STATS | |
| ID: 915296 · | |
|
I think a picture really makes it clear what the effect of the recent problems have been on the grid. SETI's growth has effectively stopped. | |
| ID: 915298 · | |
|
How about sending more of the AP 5.05 and less Seti@home 6.03. More time out in the field processing with less contacts to the sever for more work. Days worth work at a time instead of hours. | |
| ID: 915305 · | |
How about sending more of the AP 5.05 and less Seti@home 6.03. More time out in the field processing with less contacts to the sever for more work. Days worth work at a time instead of hours. This is what many people (including myself) would like. The problem is that the AP and MB WUs are split from the same input datasets. To make a long story short, the AP splitters chew through the input files FASTER than MB WUs are being processed. Two or three weeks ago we had the situation where the AP splitters had processed every single one of about 100 input files while the MB splitters were busy working on the first 10 - 20 input files! The AP splitters were basically shut down for a couple of weeks to let MB catch up on the backlog. | |
| ID: 915312 · | |
|
| |
| ID: 915319 · | |
|
Matt, | |
| ID: 915323 · | |
|
| |
| ID: 915332 · | |
|
As a scientific project the scientists in charge must keep extremely tight control of the data in order to preserve it's validity. It's not likely that they would move data to servers outside of their direct control because of this. | |
| ID: 915345 · | |
... This is 'usefull' for the science? What does this mean? The data will be calculated more enhanced/fine/accurate? BTW. This isn't an idea.. it's a question.. ;-) ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 915360 · | |
|
Having read these forums for a while I appreciate your pain. | |
| ID: 915369 · | |
Message boards : Technical News : Busy Bytes (Jul 06 2009)
| Copyright © 2013 University of California |