Would this help? <SETI connection problem>

[IBhacknU]

Here's the idea. Tell me if makes sense.

During the week, when myself and others can't connect to Berkeley, my SetiQ log is showing:

sending result
can't connect to server
will try again in 10s
downloading WU
can't connect to server
will try again in 10s
sending result
can't connect to server
will try again in 10s
repeat

Well, not exactly like that, but you get the idea.

I can't imagine this is good. Even if there are only 1500 connections allowed, all the additional attempts must be hammering the servers.

So I ask:

Is it better then to just 'attempt' to connect during the early AM hours? (instead of 24/7, every 10 seconds)
Do I disable uploading results until the weekend when I can set them free?
Do I grab a weeks worth of WUs, and then connect only once per week?

What do you think?

 

[Migroo]

Difficult question.

I wouldnt be surprised if a lot of queues are set to only try and connect in the early hours of the morning anyway.

Perhaps it would be better to change the connect times based upon what time you seem to be able to get the best performance from Berkeleys servers.

If you are concerned about hammering the servers, then lower the frequency of connects, to say once every 30 seconds or something. Leave it for a day, and observe when you are able to up/down load the most. That time is then the time that you can set your queue to connect.

Hope the logic is right!

 

[Poof]

So I ask:

Is it better then to just 'attempt' to connect during the early AM hours? (instead of 24/7, every 10 seconds)
Do I disable uploading results until the weekend when I can set them free?
Do I grab a weeks worth of WUs, and then connect only once per week?

What do you think?

I think this is a standard fix. However, unless people are using a proggy like Setiqueue (or are pointing to one), then there's no way to defer uploading off-hours. The client itself is set to keep trying every hour on the hour, forever...

Many on alt.sci.seti have claimed that over half of the SETI users run the GUI screensaver, and I expect that those GUI users probably have no clue about queueing, etc. The one positive thing that I've noticed on alt.sci.seti is that many prolific posters there have been setting up public queues for the teamless or for members of small teams... and this is a good thing.

The only other thing that I see can be done is that some ability be written in the client itself, that maybe has the client try to upload for some x number of hours and then quits. If someone wants to upload after that, it would force the manual restart of the cllient. Doing this would also put a burden on people who have remote herds who would need to point those clients to a queueing program to keep those machines fed, but then those who do that are usually members of teams too... But it WOULD stop what amounts to DDoSing by thousands of screensavers with nothing else to do but try to upload hourly.

 

[zeruty]

the problem I see with this... is that berkeley is completedly dead for a week , and then finally opens up.. say on 3:00pm on a wednesday.. all those queues that are set to upload/download early morning are screwed..... and all those queues that only upload every week are screwed

 

[Eltano1]

My Q at home is set to connect between 3.00 AM and 9.00 AM, and the one a t work I have to connect it manually every saturday between 6.00 AM and 3.00 PM.

Eltano

 

[IBhacknU]

My thoughts were directed mostly to those who use SetiQ . Even then, it's the team Q's that would make the big difference.