Blurb (Jun 26 2007)


log in

Advanced search

Message boards : Technical News : Blurb (Jun 26 2007)

Author Message
Profile Matt Lebofsky
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar
Send message
Joined: 1 Mar 99
Posts: 1389
Credit: 74,079
RAC: 0
United States
Message 593092 - Posted: 26 Jun 2007, 21:04:33 UTC

Regular outage today for backup compression/backup. Bob took care of all that. Meanwhile I briefly shut down the Network Appliance to clean its pipes, pull out some bad drives, and re-route some cables. This caused the web servers to all hang for about 5 minutes. Other than that, just playing with the new toys. New multibeam client probably won't be happening this week. Eric is still digging himself out from some long days of grant proposal writing last week.

- Matt

____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Profile Byron Leigh Hatch @ team Carl SaganProject donor
Volunteer tester
Avatar
Send message
Joined: 5 Jul 99
Posts: 3611
Credit: 11,850,493
RAC: 1,119
Canada
Message 593099 - Posted: 26 Jun 2007, 21:11:14 UTC

Matt , thank you very much for the update !

Kind Regards
Byron

Profile Dr. C.E.T.I.
Avatar
Send message
Joined: 29 Feb 00
Posts: 15993
Credit: 690,597
RAC: 0
United States
Message 593159 - Posted: 26 Jun 2007, 21:52:17 UTC - in response to Message 593092.

Regular outage today for backup compression/backup. Bob took care of all that. Meanwhile I briefly shut down the Network Appliance to clean its pipes, pull out some bad drives, and re-route some cables. This caused the web servers to all hang for about 5 minutes. Other than that, just playing with the new toys. New multibeam client probably won't be happening this week. Eric is still digging himself out from some long days of grant proposal writing last week.

- Matt


Your Post Update is Much Appreciated Sir!!! . . . Thank You and to Berkeley - CONGRATULATIONS Today . . .


____________
BOINC Wiki . . .

Science Status Page . . .

Profile kinhull
Volunteer tester
Avatar
Send message
Joined: 3 Oct 03
Posts: 1029
Credit: 636,475
RAC: 0
United Kingdom
Message 593168 - Posted: 26 Jun 2007, 22:02:24 UTC - in response to Message 593092.

Eric is still digging himself out from some long days of grant proposal writing last week.


Thanks for the info Matt.

I take it that the grant proposal is for Seti@Home, either way I wish the best of luck to Eric.
____________
Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

Profile Sir Ulli
Volunteer tester
Avatar
Send message
Joined: 21 Oct 99
Posts: 2246
Credit: 6,113,788
RAC: 420
Germany
Message 593196 - Posted: 26 Jun 2007, 22:42:40 UTC

Thanks for the UIpdate...

btw nor Probs here in Germany

Greetings from Germany NRW
Ulli

zoom314Project donor
Avatar
Send message
Joined: 30 Nov 03
Posts: 46111
Credit: 36,591,520
RAC: 5,396
Message 593336 - Posted: 27 Jun 2007, 1:32:29 UTC

Best outage I've ever seen Matt! It seemed to go off without any problems, Just as It should, Many thanks.
____________
My Facebook, War Commander, 2015

Alinator
Volunteer tester
Send message
Joined: 19 Apr 05
Posts: 4178
Credit: 4,647,982
RAC: 0
United States
Message 593664 - Posted: 27 Jun 2007, 16:32:16 UTC

The only thing I would ask is that you give us least 24 hours advance notice before rolling MB out so we can take appropriate steps. Especially for the folks (like myself) who run the Coop and other apps using the anonymous platform.

Alinator

PhonAcq
Send message
Joined: 14 Apr 01
Posts: 1622
Credit: 22,104,104
RAC: 3,978
United States
Message 593693 - Posted: 27 Jun 2007, 17:10:31 UTC

MB roll out: in addition to some leading notice, would someone also explain expected behavior. Do we need to download new clients, for example? Will we be wise to adjust our caches? Should we turn to other projects for a couple of weeks to minimize cpu cycle loss due to chaos? You know, the usual concerns.

1mp0£173
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 593718 - Posted: 27 Jun 2007, 17:32:20 UTC - in response to Message 593693.
Last modified: 27 Jun 2007, 17:33:27 UTC

MB roll out: in addition to some leading notice, would someone also explain expected behavior. Do we need to download new clients, for example? Will we be wise to adjust our caches? Should we turn to other projects for a couple of weeks to minimize cpu cycle loss due to chaos? You know, the usual concerns.

We saw this with the change from 4.x to 5.x.

For those running standard science applications (no app_info.xml), BOINC will download the new science application when it receives the first 5.2x (multibeam) work units. It will be completely automatic.

If you have an app_info.xml, and it does not specify anything for 5.2x (it should only specify versions that are known to work and not some future unreleased version that might or might not be okay), then the BOINC servers will only send 5.15.

For a while, there will be 5.15 and 5.2x units to be crunched (replacements for lost work, no quorum, etc.) and at first, there will be plenty.

As the 5.15 work gets scarce, those with an outdated science application and app_info.xml will run out of work and go idle.

In other words, this isn't a big deal. You aren't going to have days or weeks of "idle time" unless you just plain miss it -- and since most of the people asking for advance notice watch BOINC closely, I don't see that happening.

If you are really worried about the transition, delete your app_info.xml now, let BOINC revert to the standard science application, and let it manage the transition -- then update to the new chicken app. that handles multibeam.

Note that there is some need to keep both 5.15 and 5.2x "out there" or some of the earlier work units will never form a quorum and never get credit. This will likely get handled by those running the standard, non-optimized science app.
____________

Josef W. SegurProject donor
Volunteer developer
Volunteer tester
Send message
Joined: 30 Oct 99
Posts: 4230
Credit: 1,042,833
RAC: 320
United States
Message 593806 - Posted: 27 Jun 2007, 20:28:56 UTC - in response to Message 593718.
Last modified: 27 Jun 2007, 20:30:53 UTC

MB roll out: in addition to some leading notice, would someone also explain expected behavior. Do we need to download new clients, for example? Will we be wise to adjust our caches? Should we turn to other projects for a couple of weeks to minimize cpu cycle loss due to chaos? You know, the usual concerns.

We saw this with the change from 4.x to 5.x.


The change from 4.x to 5.x was more importantly a change from application name "setiathome" to "setiathome_enhanced" and the underlying processing changes which required a name change. 5.15 to 5.2x is a simple minor upgrade involving no change to the processing. Both Line feed and Multibeam WUs can be processed by either version, the science results will be the same.

For those running standard science applications (no app_info.xml), BOINC will download the new science application when it receives the first 5.2x (multibeam) work units. It will be completely automatic.

If you have an app_info.xml, and it does not specify anything for 5.2x (it should only specify versions that are known to work and not some future unreleased version that might or might not be okay), then the BOINC servers will only send 5.15.

For a while, there will be 5.15 and 5.2x units to be crunched (replacements for lost work, no quorum, etc.) and at first, there will be plenty.

As the 5.15 work gets scarce, those with an outdated science application and app_info.xml will run out of work and go idle.

In other words, this isn't a big deal. You aren't going to have days or weeks of "idle time" unless you just plain miss it -- and since most of the people asking for advance notice watch BOINC closely, I don't see that happening.


If you are really worried about the transition, delete your app_info.xml now, let BOINC revert to the standard science application, and let it manage the transition -- then update to the new chicken app. that handles multibeam.

Note that there is some need to keep both 5.15 and 5.2x "out there" or some of the earlier work units will never form a quorum and never get credit. This will likely get handled by those running the standard, non-optimized science app.

Red = generalizing from a different situation, so off-track.

The new apps will convert internal flop counts to the reported fpops_cumulative at a 13.7% higher multiple. Multibeam work is enough different that RAC would decline if an adjustment weren't made. That is the only difference which need concern users, if they stay with the old application they'll be claiming lower credits than others and generating much wrath.

The only other change is that those using graphics will see "SETI@home Multi-beam" at the top of the Pillars display when doing MB work, and the data source will be reported as from a particular beam and polarity.
Joe

PhonAcq
Send message
Joined: 14 Apr 01
Posts: 1622
Credit: 22,104,104
RAC: 3,978
United States
Message 593895 - Posted: 27 Jun 2007, 22:10:44 UTC

So it sounds like if I do nothing, then I will not see a difference at first, but in time, as the 5.15 wu's run out I will see more MB wu's and a general decrease in RAC. This latter effect will be remedied by moving to an MB updated application. But if the reduction in RAC was not important to me, then I could continue running my optimized app for the foreseable future, without any changes.

Right?

Josef W. SegurProject donor
Volunteer developer
Volunteer tester
Send message
Joined: 30 Oct 99
Posts: 4230
Credit: 1,042,833
RAC: 320
United States
Message 593909 - Posted: 27 Jun 2007, 22:37:07 UTC - in response to Message 593895.

So it sounds like if I do nothing, then I will not see a difference at first, but in time, as the 5.15 wu's run out I will see more MB wu's and a general decrease in RAC. This latter effect will be remedied by moving to an MB updated application. But if the reduction in RAC was not important to me, then I could continue running my optimized app for the foreseable future, without any changes.

Right?

Yes. But of course we hope users will upgrade to the new optimized app quickly. We expect it to be slightly faster so even those who are strictly interested in producing more science results will be motivated to upgrade.
Joe

1mp0£173
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 594114 - Posted: 28 Jun 2007, 2:29:49 UTC - in response to Message 593806.


Red = generalizing from a different situation, so off-track.

We'll see....

____________

Message boards : Technical News : Blurb (Jun 26 2007)

Copyright © 2014 University of California