Well, the network graphs show plenty of traffic, but the splitters are still barely keeping up & are unable to build a ready to send buffer.
Almost all of my Scheduler requests today have resulted in No work available messages.
Actually the inbound traffic is very high at the moment, similar to the 27th when work output was severely limited.

---

Grant
Darwin NT

Raistmer posted this message from Eric over on Lunatics forums...

We're having some problems with the AstroPulse database. Everything astropulse related is down. Don't know when it will be back up.

Eric

---

PROUD MEMBER OF Team Starfire World BOINC

I guess some have realized that.

---

With each crime and every kindness we birth our future.

I guess some have realized that.

Nah, could never had guessed that :-)

So, here I sit with my main cruncher full of (over 90) AP tasks, + all the finished ones, and they will get validated in between now and kingdom comes. That's what I get for trying to go AP only with my ATI GPU cruncher.

I guess it's time to let it feed on some MB tasks too then, until AP is back.

To put it simple: CRAP

Don't do that in here, it will smell bad! :)
I was going to do some playing with AP on my cards as well, but I guess that will just wait until the servers feel happy again.

---

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

Raistmer posted this message from Eric over on Lunatics forums...

We're having some problems with the AstroPulse database. Everything astropulse related is down. Don't know when it will be back up.

Eric

So the question is "Why are the problems with the AP database limiting MB work production?"

---

Grant
Darwin NT

Raistmer posted this message from Eric over on Lunatics forums...

We're having some problems with the AstroPulse database. Everything astropulse related is down. Don't know when it will be back up.

Eric

So the question is "Why are the problems with the AP database limiting MB work production?"

I don't think the two are related. As far as MB work goes it would seem there is a lack of data. Compound that with the fact a lot of the data we are getting seems to be shorties. At least I'm seeing shorties on my 8500GT. Tasks running 30 min instead of the normal 2 hours 15 min.

My total task count is way up as well. I have about 8600 total tasks where I normally see around 5000. Also instead of having 200-300 AP tasks that is down to about 50.

---

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

So the question is "Why are the problems with the AP database limiting MB work production?"

Big thing is the fact that the AP units take up disk space and are not being removed.

Data Distribution State	                     SETI@home #	Astropulse #	As of*
Results ready to send	                       459	             0	        0m
Current result creation rate	             27.5117/sec	0.0203/sec	6m
Results out in the field	               6,263,413	131,639	        0m
Results received in last hour	                70,135           861	        0m
Result turnaround time (lha)	               70.40 hours	117.04 hours	0m
Results returned and awaiting validation       6,745,334	205,267	        0m
Workunits waiting for validation                    26	         37,297	        0m
Workunits waiting for assimilation               963,765	   69	        0m
Workunit files waiting for deletion                3	            0     	0m
Result files waiting for deletion                   69	            0	        0m
Workunits waiting for db purging                1,111,915	   102	        0m
Results waiting for db purging	               2,355,746	  1,663  	0m

---

Matt(?) reported a short time ago that there was a problem affecting AP units that caused not only the passage of the returned (AP) results to stall, but was causing collateral problems elsewhere. It would appear that the deliberate act of stopping all AP related server side activity is in itself causing a slowdown in the production of MB workunits as the rate of their production is now way down (see Arkayn's previous post for a typical server status).
Let us hope that the S@H staff are able to bottom this problem out in a reasonable time frame allowing normal production and processing can resume.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

As far as MB work goes it would seem there is a lack of data.

There's no lack of data, the problem is splitting what is available in order to make Work Units. For whatever reason, the splitters just aren't able to crank up Work Unit output like they normally do.

---

Grant
Darwin NT

Exactly what I meant. I should have said something along the lines "split data to send".

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

It looks like things have been getting cleared out. The amount of AP "Workunits waiting for db purging" has gone down a lot in the past 10 hours. While AP "Results waiting for db purging" have gone down a bit.

[As of 8 Jul 2011 | 15:00:08 UTC] 
Data Distribution State				SETI@home #		Astropulse #
Results ready to send				   17,650		      9
Current result creation rate			       31.7752/sec	      0.0109/sec
Results out in the field			6,429,254		123,495
Results received in last hour			   73,664		    882
Result turnaround time (last hour average)	       71.70 hours	    127.53 hours
Results returned and awaiting validation	6,557,407		213,932
Workunits waiting for validation		        4		 41,455
Workunits waiting for assimilation		  835,113		    116
Workunit files waiting for deletion		       70		      0
Result files waiting for deletion		       49		      0
Workunits waiting for db purging		1,095,471		     28
Results waiting for db purging			2,307,718		  1,414

---

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