Wet Weekend (Jan 07 2008)

Message boards : Technical News : Wet Weekend (Jan 07 2008)

To post messages, you must log in.

AuthorMessage
Profile Matt Lebofsky
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 1 Mar 99
Posts: 1441
Credit: 213,689
RAC: 0
United States
Message 698245 - Posted: 7 Jan 2008, 23:28:38 UTC

Lots of weather in the Bay Area over the weekend, leading to many power outages. Luckily our project was not affected.

The new pseudo-random nature of our workunit creation finally worked itself out, and we were sending data at a relatively even pace. Speaking of sending data... At the end of last week my suspicions were confirmed: the router between us and our ISP (a Cisco 2811) has been CPU bound for who-knows-how-long, thus causing an artificial 60 Mbit/sec cap on our outbound packets. Further research will determine whether we can improve its performance or if we need to procure a better router.

We had an assimilator get jammed on a broken result. I had to delete the result to clear the pipes. This happened once before a week or two ago. A little detective work this morning uncovered that both such broken results were processed by optimized clients. I'm just sayin'. This could easily be a conincidence.

Spent a large chunk of the day trying to coax another Intel-donated server to life. We've gotten a lot of stuff from Intel recently, all in varying states of functionality (some missing CPUs, some have test boards, etc.). This particular one (4 2.66GHz CPUs, 8 GB RAM) was dead in the water for a while as it wouldn't respond to any keyboard/mouse. However, the other day I noticed one of the front-side fan modules wasn't seated properly. I adjusted it, and now the server sees all input devices. It's still a little squirly, but may be a worthwhile web server after all. We're calling it "maul" (sticking to the current "darth" theme). I'll announce it again if it actually proves to be ready for prime time.

- 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
ID: 698245 · Report as offensive
Profile Dr. C.E.T.I.
Avatar

Send message
Joined: 29 Feb 00
Posts: 16015
Credit: 749,515
RAC: 220
United States
Message 698288 - Posted: 8 Jan 2008, 1:56:24 UTC


Matt - keep up the great work Sir . . . lucky 'bout that rain too, eh (re: no damage)

stay well


BOINC Wiki . . .

Science Status Page . . .
ID: 698288 · Report as offensive
seti@elrcastor.com
Volunteer tester

Send message
Joined: 30 Jan 00
Posts: 35
Credit: 4,879,559
RAC: 0
United States
Message 698296 - Posted: 8 Jan 2008, 3:53:18 UTC
Last modified: 8 Jan 2008, 3:53:30 UTC

googled "2811 throughput" and found

http://www.derkeiler.com/Mailing-Lists/Firewall-Wizards/2006-10/msg00027.html

that said "the 2811 throughput is 61.44 Mbps"
ID: 698296 · Report as offensive
Profile Sharkbait

Send message
Joined: 2 Jun 99
Posts: 11
Credit: 1,353,312
RAC: 4,176
United States
Message 698322 - Posted: 8 Jan 2008, 5:36:47 UTC

Matt,

You upped the ready to send queue to 1 million, but it seems to be hitting a cap at about 800,000. Is that a computing limitation?

Good workings!

Ben
ID: 698322 · Report as offensive
djmotiska

Send message
Joined: 26 Jul 01
Posts: 18
Credit: 6,281,441
RAC: 4,643
Finland
Message 698368 - Posted: 8 Jan 2008, 8:46:58 UTC - in response to Message 698245.  

At the end of last week my suspicions were confirmed: the router between us and our ISP (a Cisco 2811) has been CPU bound for who-knows-how-long, thus causing an artificial 60 Mbit/sec cap on our outbound packets.


So the problem was with router, as I suspected in previous thread. Glad to see you found the cause of the problem, hopefully you can fix it. OTOH, I hope my post (my first post) helped you.
ID: 698368 · Report as offensive

Message boards : Technical News : Wet Weekend (Jan 07 2008)


 
©2016 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.