• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

S@H daily team stats 01/30

Hellburner

Senior Member <br>Elite Member
Local group production 01/30:

09 HW France...................(+473024).................. +2681
10 S@N.............................(+394246).................. +5114
11 TA.................1677278...................................... +4888
12 Planetary..........................(-72402).................. +1404
13 Intel.................................(-129290).................... +350
14 M$...................................(-134032).................... +650
15 IBM.................................(-189626).................. +1466
16 DSL................................(-316760).................. +2033

Four new members 🙂 outage at Berkeley kept the numbers low.
 
1st

First time this year under 5000 ??

What are you guys doing this morning, almost ten minutes and still no other replies.😕
 
Low numbers for everyone today. 🙁

That's alright though! We're still higher than the previous upper 2k stats from just a few months ago. 🙂

I'm thinking it's just a glitch in the system. 😛

Keep it up everyone!!

(Thanks HB)

--LANMAN
 
Not bad, considering that there were over 1000 WU's in OK's as of 5 am this morning....still there?!

(Just checked...down to 219 now...so it's looking better 🙂 ...I'm showing 4300 since 4:30 PM yesterday (Eastern time))


Thanks HB! 🙂

Not to mention other Queue's that may have them stuck also! 🙁

Oh well...there will be a flood sooner or later! :Q

Thanks again...

Go TeAm! 🙂
 
Thanks HB!

My queue has been dumping without much problem since I was able to get remote clients to connect to it.

I'm moving my fleet off OK's proxy so I can free up his resources for other AT members.
 
Ditto what others are saying about Berkeley. I've got almost a full day's worth of WU's -- 247! -- stacked up in my Q that I cannot get uploaded to Berkeley.

-baz
 
My Q was only doing 1 or so every hour (if even that) as late as 3:30 AM CST this morning but I noticed they are all uploaded/downloaded now. Is there a pattern to this. Is there a time period we should just not try to transmit?
 
Thanks HB

Berkeley's problems are affecting everone I see

Had 900+ wu waiting to send this am before work (4:30am)and 500+ waiting now..............from 5:49am and on........so the 900 took all day to load to Berkeley 🙁

Ahhhhh well..........soon the uncommited will fold and leave more bandwidth for the dedicated 🙂


😎 😎
 
Well, the numbers may be low but we still did better than most around us. 😀

Welcome new members and thanks Hellburner!
 
Thanks HB 🙂

'Only' 5 k ,oh well................ 😉

Smoke ball

Is there a pattern to this. Is there a time period we should just not try to transmit?
Yes & yes ,look at this I copied from the SETI site

January 29, 2002

The campus wide outbound bandwidth cap is set at 70Mb/s. We are getting only around 10Mb/s of this during the day but are getting all we need at night. The best time for connecting varies but is roughly for the 2 hours on either side of 1:00 PST, or 9:00 UT.

January 25, 2002

Users may find their connections to the server slow during peak hours. Some may even see a connection refusal. This is due to a bandwidth limit between UC Berkeley and the Internet. The aggregate Internet usage over the entire campus has recently hit this limit. UC Berkeley's Communication and Network Services has been extremely helpful in working with us on this issue. The goal is for SETI@home users to get as good a data rate as possible while at the same time not adversely affecting the rest of campus. The current (new) policy is for SETI@home to get all excess capacity in outbound bandwidth (inbound is not an issue). This is being done by placing our traffic at a lower priority than that of other users, but applying no rate limit other than the campus wide cap. Placing us at a lower priority is necessary so that interactive Internet users do not experience painfully high latency. This policy translates into enormous capacity at (local) night, but a tight squeeze during peak hours. Thus far this policy is working better than expected even though there may be periods of poor service. Please bear with us as we work towards a sustainable long term solution.


Taken from their Tech news site

Here is the link for SETI Bandwidth useage again 🙂

I was gonna do a new post on it but I heard there were already some threads about it ,I couldn't see them though.
You seen any threads about it?
What time is there quoted times in GMT?
 
It looks like all the teams' production is down today--no doubt due to bandwidth issues. Thanks, HB. 🙂


Late last year, they raised the bandwidth cap for the ResHalls from 30Mbps to 40Mbps. Internet speeds sucked big time before they raised the cap, and they only became slightly better after raising the cap because students just increased their usage to consume the new speeds. So, now they're trying to negociate with the UC network internet provider to get the ResHalls up to 45Mbps because things still slow down to speed of molasses here in the evenings.

The only solutions I see are to restrict the usage of file-sharing programs like Morpheus (which I hope they don't do, but would significantly improve network performance) or they could purchase more bandwidth. The first one is probably more likely.

As this relates to SETI, I would guess that if things continue as they have over the past week or so, the folks at S@H will do something to improve the bandwidth situation, and they'll do it soon.

For now, the best time to upload is from 2AM PST to ~6AM PST.
 
For the first time, SetiDriver didn't flush overnight. So I set the proxy to OrangeKid's. I'll check tomorrow to see if that helps (so far in 10 minutes it hasn't, but I'm hopeful since the button changed to
"Stop Transmit"
 
Back
Top