Where are the flowing WUs

Message boards : Number crunching : Where are the flowing WUs
Message board moderation

To post messages, you must log in.

AuthorMessage
mags1951
Avatar

Send message
Joined: 31 Aug 03
Posts: 64
Credit: 7,721
RAC: 0
United Kingdom
Message 26425 - Posted: 14 Sep 2004, 17:09:30 UTC

I would call it more of a trickle. My last few cobblestones were just that, going up by one each time. Unfotunately we STILL cannot see pending or results - oh yes its because of the system load.

Since this is more of a Beta test than anything else, would it not make sense to allow sight of these results (we have never had them here only on the Beta site). The users would be able to give better input to the errors that may or may not be happening if they could see the results.
<IMG><IMG><img>
ID: 26425 · Report as offensive
Pascal, K G
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 2343
Credit: 150,491
RAC: 0
United States
Message 26430 - Posted: 14 Sep 2004, 17:28:53 UTC

Give it a rest jeeezzzzzz!!!


My name is Pascal and this message has my approval...

It is 10 oclock, do you know what your WUWUs are doing tonight...

ID: 26430 · Report as offensive
GvdM

Send message
Joined: 21 Sep 03
Posts: 36
Credit: 40,227
RAC: 0
United States
Message 26436 - Posted: 14 Sep 2004, 17:36:11 UTC - in response to Message 26425.  
Last modified: 14 Sep 2004, 17:37:14 UTC

> I would call it more of a trickle. My last few cobblestones were just that,
> going up by one each time. Unfotunately we STILL cannot see pending or
> results - oh yes its because of the system load.
>
> Since this is more of a Beta test than anything else, would it not make sense
> to allow sight of these results (we have never had them here only on the Beta
> site). The users would be able to give better input to the errors that may or
> may not be happening if they could see the results.
> [/url]
ID: 26436 · Report as offensive
Profile Julian

Send message
Joined: 19 Jul 99
Posts: 75
Credit: 2,470,428
RAC: 0
United Kingdom
Message 26439 - Posted: 14 Sep 2004, 17:51:45 UTC

I had them all. One of our computers reached its download limit today! Yes our magnificent celeron 900Mhz (or there abouts) was downloading and crunching unis in about 30 seconds each. Somehow you know I think either one of our students slipped in a home designed quantum computer processor or the units were a bit iffy. Anyway when I saw it the thing was sitting doing nothing and SETI would not let it have anything to crunch. Oh for the day of classic when I would have crunched 50 units in under 1 hour on such a machine. Anyone else getting iffy units, this was my only machine to do it but the others were crunching earlier units and I don't know if they downloaded any dross.
ID: 26439 · Report as offensive
Profile Paul D. Buck
Volunteer tester

Send message
Joined: 19 Jul 00
Posts: 3898
Credit: 1,158,042
RAC: 0
United States
Message 26525 - Posted: 14 Sep 2004, 22:42:24 UTC - in response to Message 26436.  

> Since pendings seem to work well on predictor then maybe it would be a good
> idea to bring them back and work out the problems. I do not see the load on
> this project getting any less, only growing in the future.

George,

Predictor, LHC, and Pirates have all limited their number of participants. So, it should be no surprise that there are no issues there with pending credit. There were no problems in SETI during the beta with pending credit also.

The problem with many of these issues is that the "load" on system components is that the resultant load is usually non-linear. Add 1,000 users and have load "x", add another 1,000 and it is 1.1 * 'x' + 'x'; with the multiplier going up at each additional group.

I don't know what the actual working group size is at this time on SETI, but the last number I had any faith in was well over 30,000 ...

<p>
For BOINC Documentaion: Click Me!


ID: 26525 · Report as offensive
GvdM

Send message
Joined: 21 Sep 03
Posts: 36
Credit: 40,227
RAC: 0
United States
Message 26530 - Posted: 14 Sep 2004, 22:58:20 UTC - in response to Message 26525.  

> > Since pendings seem to work well on predictor then maybe it would be a
> good
> > idea to bring them back and work out the problems. I do not see the load
> on
> > this project getting any less, only growing in the future.
>
> George,
>
> Predictor, LHC, and Pirates have all limited their number of participants.
> So, it should be no surprise that there are no issues there with pending
> credit. There were no problems in SETI during the beta with pending credit
> also.
>
> The problem with many of these issues is that the "load" on system components
> is that the resultant load is usually non-linear. Add 1,000 users and have
> load "x", add another 1,000 and it is 1.1 * 'x' + 'x'; with the multiplier
> going up at each additional group.
>
> I don't know what the actual working group size is at this time on SETI, but
> the last number I had any faith in was well over 30,000 ...
>

Paul,

I am aware of the participant and load issues. My point was that the load on seti is only going to increase as time goes on so might as well do it now. Get the bugs worked out. If it goes down due to load issues it would hardly be a surprise, it does that now as I think a few have noticed. As load increases with more and more participants that type of logic would suggest that pending credit would never come back.

George
ID: 26530 · Report as offensive
Profile Paul D. Buck
Volunteer tester

Send message
Joined: 19 Jul 00
Posts: 3898
Credit: 1,158,042
RAC: 0
United States
Message 26724 - Posted: 15 Sep 2004, 10:03:00 UTC - in response to Message 26530.  

> I am aware of the participant and load issues. My point was that the load on
> seti is only going to increase as time goes on so might as well do it now. Get
> the bugs worked out. If it goes down due to load issues it would hardly be a
> surprise, it does that now as I think a few have noticed. As load increases
> with more and more participants that type of logic would suggest that pending
> credit would never come back.

George,

George, I agree with you. The problem is that right now we are having to live with a problem called "legacy code" and that is the main stumbling block. We have an infrastructure that needs a change and contrary to some of the nay-sayers, this is a tough issue.

For example, I took the design team and coders to task for the structure of the results table some time in the past. The good news is that most, if not all, of my criticisms were accepted as being valid. The problem is that we are driving down the road at 600 miles an hour... so how do we change the flat tire?

For the massive restructuring of the results table would make changes to all of the modules that read or write to that table, then we have the data that would require migration. So, do we take the project off line while we do this? How long do we test the changes before going live again? and so on, and so on ...

I have thought about this and I know that we could do a side-step into changes, but we still have the issue right now that the system is also near the edge of ability to keep up with current demand. With many other tasts still to go, I am not sure if this is the right time to do a lot of expirimentation with changes to the schema and migration of data.

Since I am only an external observer like the rest of the participants I cannot see what tasks that are being pursued at this time. Though, from appearances we are still doing a lot of client work to solve issues with stability, and enhancements to the web site. All of these are, seem to me, to be the proper things to be doing at this time.

Granted, this issue has to be solved (Paul's opinion) before the closing of the SETI@Home Classic project. But I don't think we are super close to that yet.


<p>
For BOINC Documentaion: Click Me!


ID: 26724 · Report as offensive

Message boards : Number crunching : Where are the flowing WUs


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.