Panic Mode On (80) Server Problems?

Cannot see anything wrong on cricket or server status but last three report/requests have
23/01/2013 18:14:39 | SETI@home | Scheduler request failed: HTTP service unavailable

First was at 18:04:03

Sever status shows green, but inbound & outbound traffic have hit bottom.

Possible reporting blip starting?
Cricket "bits out" definitely heading southwards.

Why is it that as soon as APs start generating, everything goes south? Normal u/d loads until then. Has anyone given any thought of compressing these WUs and then having the apps uncompress once received at the users machine? Doesn't Einstein use something like this to send their large packets?
____________


I don't buy computers, I build them!!

Why is it that as soon as APs start generating, everything goes south? Normal u/d loads until then. Has anyone given any thought of compressing these WUs and then having the apps uncompress once received at the users machine? Doesn't Einstein use something like this to send their large packets?

Why is it that as soon as APs start generating, everything goes south? Normal u/d loads until then. Has anyone given any thought of compressing these WUs and then having the apps uncompress once received at the users machine? Doesn't Einstein use something like this to send their large packets?

Yes, people have thought about it - and the answer is that even with LZMA compression (7-zip), you only save about 3% of the 8MB file size. Try it for yourself - the WUs are practically incompressible, or to put it another way, they're already compressed almost as far as it's possible to compress them.

Mind you - you very rarely get a WU that will compress down to half its original size. They (almost?) always come from the B3_P1 channel, and indicate that once again a bit has got stuck at the receiver or in the Aercibo antenna cabling. The data is useless, and the task will overflow in seconds - it's a useful diagnostic test.

Since 15:00 U.T.C. one of my machine has been getting scheduler request failures is there something wrong or is my timing for new work wrong
____________

Or could it be that the servers are tuned for working with 366kb files and not 8mb files, never mind a mixture of the two?
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

So then the simple answer is that processing AP's is a test of band width capabilities for SETI, and that seemingly each time that happens the bandwidth is found inadequate.


I suppose, absent increasing bandwidth, there really is only a single solution to this.

Curious that this conclusion is as yet undetected.

And no, I don't run AP's -- don't want to be part of the problem there.