The new Cricket graph seems to balance on the same speed as the old over this few first hours. Will be interesting to see if more bandwidth is used in the long run or if the servers need to be upgraded.

I think a donation drive is easier to perform now that the bandwidth issue are removed from the project.

---

The new Cricket graph seems to balance on the same speed as the old over this few first hours. Will be interesting to see if more bandwidth is used in the long run or if the servers need to be upgraded.

I think a donation drive is easier to perform now that the bandwidth issue are removed from the project.

Each donation is always welcome.

See here.

http://setiathome.berkeley.edu/forum_thread.php?id=71030&postid=1353226#1353226

---

With each crime and every kindness we birth our future.

Hi!
I have a question: in the new location can we have a graph like this http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw%3Am%3Ay;view=Octets?

---

Hi!
I have a question: in the new location can we have a graph like this http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw%3Am%3Ay;view=Octets?

You mean like the one listed here & here?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Yes. Sorry, I was finding "graph" instead of "cricket" but 1 minute after my question I have found it.

FF

---

It seems we are exploring other was of throttling the bandwidth from the servers by restricting work out. One would think that due to lost connections and retries with the old throttling method (at the switch) that more work is flowing out, is that true or is it about the same?

seems to be the same, except when i get work i'm able to download it quickly...

---

It seems we are exploring other was of throttling the bandwidth from the servers by restricting work out. One would think that due to lost connections and retries with the old throttling method (at the switch) that more work is flowing out, is that true or is it about the same?

seems to be the same, except when i get work i'm able to download it quickly...

Matt's most recent message indicates a limit on the download server disk i/o. so other limits were put in place to keep it down.
That might just be due to the servers getting settled in & a lot of i/o traffic at the moment. We will just have to wait and see if disk i/o will be the bottle neck in using more bandwidth.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I have multiple clients running, and out of all of them, 1 still have not got any tasks. Below is what I get every time in the logs.. I have restarted my PC also, to make sure that wasn't the issue. I have been unable to retrieve any new tasks on this system. Any suggestions on what I can do to start getting tasks again ?

4/4/2013 7:25:42 | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 7:25:42 | SETI@home | Requesting new tasks for CPU
4/4/2013 7:25:44 | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 7:25:44 | SETI@home | Project has no tasks available
4/4/2013 7:26:14 | SETI@home | update requested by user
4/4/2013 7:26:19 | SETI@home | Sending scheduler request: Requested by user.
4/4/2013 7:26:19 | SETI@home | Requesting new tasks for CPU and ATI
4/4/2013 7:26:20 | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 7:26:20 | SETI@home | Project has no tasks available

---

I have multiple clients running, and out of all of them, 1 still have not got any tasks. Below is what I get every time in the logs.. I have restarted my PC also, to make sure that wasn't the issue. I have been unable to retrieve any new tasks on this system. Any suggestions on what I can do to start getting tasks again ?

4/4/2013 7:25:42 | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 7:25:42 | SETI@home | Requesting new tasks for CPU
4/4/2013 7:25:44 | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 7:25:44 | SETI@home | Project has no tasks available
4/4/2013 7:26:14 | SETI@home | update requested by user
4/4/2013 7:26:19 | SETI@home | Sending scheduler request: Requested by user.
4/4/2013 7:26:19 | SETI@home | Requesting new tasks for CPU and ATI
4/4/2013 7:26:20 | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 7:26:20 | SETI@home | Project has no tasks available

It is very easy. You must wait. We are recovering from an extended outage & apparently some limits were put on work generation/sending out. Until the servers back log clears up. Maybe by later today or tomorrow things will start to get back to normal.
Currently I have 4 out of 27 machines without SET@Home work.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Looks like we are up to 160Mbit/s now and thats a fair increase. During next week we should be able to see the new bandwidth usage. This week will probably be a little special because of the 3 day down time.

---

IF we truly, finally, have bandwidth out of the way as the limiting factor in work distribution, Matt can finally concentrate on finding and hopefully fixing any other bottlenecks that are found. Such as the i/o problem which he has mentioned.

Full speed ahead, Seti!!!


Meows and away!

---

"Time is simply the mechanism that keeps everything from happening all at once."

04/04/2013 18:25:29 | SETI@home | Started download of 30jn12ad.24555.92854.206158430216.10.40
04/04/2013 18:25:29 | SETI@home | Started download of 30jn12ad.24555.92854.206158430216.10.139
04/04/2013 18:25:32 | SETI@home | Finished download of 30jn12ad.24555.92854.206158430216.10.40
04/04/2013 18:25:33 | SETI@home | Finished download of 30jn12ad.24555.92854.206158430216.10.139


Im well and truly impressed, I just hope it can stay that good! :)

---

Things were looking great here, then went belly up. One machine grabbed a full cache of CUDA tasks, a few replacements...now nothing. The other machine got a few ATI APs, a couple CPU APs, but No CUDA MBs. Then it dried up. When it's full, it should be around 180 tasks, mostly APs. They are going fast...

Where's the Beef?

4/4/2013 12:51:17 AM | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 12:51:17 AM | SETI@home | Requesting new tasks for NVIDIA and ATI
4/4/2013 12:51:19 AM | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 12:51:19 AM | SETI@home | Project has no tasks available
4/4/2013 12:59:24 AM | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 12:59:24 AM | SETI@home | Requesting new tasks for ATI
4/4/2013 12:59:25 AM | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 12:59:25 AM | SETI@home | Project has no tasks available
4/4/2013 1:06:30 AM | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 1:06:30 AM | SETI@home | Requesting new tasks for NVIDIA
4/4/2013 1:06:32 AM | SETI@home | Scheduler request completed: got 0 new tasks
4/4/2013 1:06:32 AM | SETI@home | Project has no tasks available
...

I'm finally seeing some action since yesterdays start-up. Usually I have a full cache after a few hours, back then it took 12 minutes to download 8 AstroPulses. Since the move, it's around 12 SECONDS to download 8 AstroPulses...When they send them.

4/4/2013 1:37:28 PM | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 1:37:28 PM | SETI@home | Requesting new tasks for CPU and NVIDIA and ATI
4/4/2013 1:37:30 PM | SETI@home | Scheduler request completed: got 4 new tasks
4/4/2013 1:37:32 PM | SETI@home | Started download of ap_24jn12ac_B5_P1_00372_20130403_02027.wu
4/4/2013 1:37:32 PM | SETI@home | Started download of ap_24jn12ad_B2_P0_00291_20130403_12729.wu
4/4/2013 1:37:32 PM | SETI@home | Started download of ap_24jn12ac_B5_P0_00373_20130403_01859.wu
4/4/2013 1:37:32 PM | SETI@home | Started download of ap_24jn12ac_B5_P1_00373_20130403_02027.wu
4/4/2013 1:37:41 PM | SETI@home | Finished download of ap_24jn12ac_B5_P1_00372_20130403_02027.wu
4/4/2013 1:37:43 PM | SETI@home | Finished download of ap_24jn12ac_B5_P0_00373_20130403_01859.wu
4/4/2013 1:37:45 PM | SETI@home | Finished download of ap_24jn12ad_B2_P0_00291_20130403_12729.wu
4/4/2013 1:37:45 PM | SETI@home | Finished download of ap_24jn12ac_B5_P1_00373_20130403_02027.wu
4/4/2013 1:42:35 PM | SETI@home | Sending scheduler request: To fetch work.
4/4/2013 1:42:35 PM | SETI@home | Requesting new tasks for CPU and NVIDIA and ATI
4/4/2013 1:42:40 PM | SETI@home | Scheduler request completed: got 3 new tasks
4/4/2013 1:42:43 PM | SETI@home | Started download of ap_24jn12ac_B6_P0_00010_20130403_08724.wu
4/4/2013 1:42:43 PM | SETI@home | Started download of ap_24jn12ad_B2_P0_00306_20130403_12729.wu
4/4/2013 1:42:43 PM | SETI@home | Started download of ap_24jn12ac_B6_P0_00009_20130403_08724.wu
4/4/2013 1:42:52 PM | SETI@home | Finished download of ap_24jn12ad_B2_P0_00306_20130403_12729.wu
4/4/2013 1:42:53 PM | SETI@home | Finished download of ap_24jn12ac_B6_P0_00010_20130403_08724.wu
4/4/2013 1:42:53 PM | SETI@home | Finished download of ap_24jn12ac_B6_P0_00009_20130403_08724.wu
4/4/2013 1:47:48 PM | SETI@home | No tasks are available for AstroPulse v6
4/4/2013 1:54:55 PM | SETI@home | No tasks are available for AstroPulse v6
4/4/2013 1:54:55 PM | SETI@home | No tasks are available for the applications you have selected....

After a few APs were sent yesterday, I calculated it would take around 2 minutes to send me my 88 ATI APs. I'm still waiting...

RutRoe, looks like someone tripped over a wire;

4/4/2013 2:13:51 PM | SETI@home | Scheduler request failed: Couldn't connect to server
4/4/2013 2:17:00 PM | SETI@home | Scheduler request failed: Failure when receiving data from the peer
4/4/2013 2:25:07 PM | SETI@home | Scheduler request failed: Couldn't connect to server
4/4/2013 2:27:25 PM | SETI@home | Scheduler request failed: Couldn't connect to server

:-(

here in austria it was nearly impossible to download any wu - only with a proxy. but it was always a struggle with all the free proxies to get / keep it working... since the relocation there are no more problems at all - the downloadspeed is amazing!

keep up the good work

---

Matt's most recent message indicates a limit on the download server disk i/o. so other limits were put in place to keep it down.
That might just be due to the servers getting settled in & a lot of i/o traffic at the moment. We will just have to wait and see if disk i/o will be the bottle neck in using more bandwidth.

Even if the actual downloads are still restricted to about 100Mb, the extra bandwidth available for overhead should eliminate the network congestion and speed things up a LOT. The network wonks arond here have been saying for a while that a network really only works efficiently up to about 70% of its nominal capacity.

That said, I see the crickets spiked at about 170Mb and did not drop all the way back down to 95, so something must have been changed.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

it will be very interesting to see the cricket graphs after everything settles in, i bet it is below 90Mb/s

---

it will be very interesting to see the cricket graphs after everything settles in, i bet it is below 90Mb/s

I'm thinking my initial estimates were wrong, and it will closer to what it is now- around 130Mb/s. Higher if it's a shortie storm, lower if they're mostly VLARs, but around 130Mb/s the rest of the time.

---

Grant
Darwin NT

it will be very interesting to see the cricket graphs after everything settles in, i bet it is below 90Mb/s

I'm thinking my initial estimates were wrong, and it will closer to what it is now- around 130Mb/s. Higher if it's a shortie storm, lower if they're mostly VLARs, but around 130Mb/s the rest of the time.

I'm imagining a much higher rate after everything settles in, long term. How many people had their machines partially, or even fully dedicated to other projects due to the difficulty of getting SETI work units? As the word gets around that it's possible to get work regularly and quickly, I bet a goodly number of people might return, and there might even be a few heavyweight crunchers amongst them.

it will be very interesting to see the cricket graphs after everything settles in, i bet it is below 90Mb/s

I'm thinking my initial estimates were wrong, and it will closer to what it is now- around 130Mb/s. Higher if it's a shortie storm, lower if they're mostly VLARs, but around 130Mb/s the rest of the time.

Well, it's just dropped down to about 87 Mbps -- at the same time as the number of AP workunits waiting to send dropped to zero. Which is consistent with what we used to see.

---

Posted yesterday at SETI Beta by Eric Korpela:

Our new network connection should be able to handle about 5 times the bandwidth of the old one. We're currently running it at about half capacity.

Ref http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2008&postid=45421#45421

                                                                   Joe