Panic Mode On (80) Server Problems?

A quick sum
Number of MB tasks produced per second ~60 (based on an average production rate of 30WU/s)
Amount of MB data to be transferred per second = 60*366 = 22000KB
Now that's only 22MB per second, which leaves a fair bit of change from the 100KBs pipe.

So what is gobbling up the other 78MB???
My sums ignore overheads, even if these run at 100% of the "real" data there is something having a fair old feast at the expense of S@H's link between the lab and the outside world....
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

A quick sum
Number of MB tasks produced per second ~60 (based on an average production rate of 30WU/s)
Amount of MB data to be transferred per second = 60*366 = 22000KB
Now that's only 22MB per second, which leaves a fair bit of change from the 100KBs pipe.

So what is gobbling up the other 78MB???
My sums ignore overheads, even if these run at 100% of the "real" data there is something having a fair old feast at the expense of S@H's link between the lab and the outside world....

A quick sum
Number of MB tasks produced per second ~60 (based on an average production rate of 30WU/s)
Amount of MB data to be transferred per second = 60*366 = 22000KB
Now that's only 22MB per second, which leaves a fair bit of change from the 100KBs pipe.

So what is gobbling up the other 78MB???
My sums ignore overheads, even if these run at 100% of the "real" data there is something having a fair old feast at the expense of S@H's link between the lab and the outside world....

Check your bits and bytes.

22 MegaBytes (normal unit for file sizes and storage)
is a lot more than
100 Megabits (normal unit for communications channels)

In that case why do we get reasonable download rates sometime when the splitters are going all out, and yet others (like now) the performance is very poor?
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

In that case why do we get reasonable download rates sometime when the splitters are going all out, and yet others (like now) the performance is very poor?

An AP is about 22 times the size of an MB.
It could be that the presence of a feed of APs just trips things over the line. Likewise a high demand, such as a shortie storm has the same effect.
A small perturbation is just enough to upset the scheduler, which causes a higher number of "rejects" than normal, and so the snowball of delays and retries grows.
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

In that case why do we get reasonable download rates sometime when the splitters are going all out, and yet others (like now) the performance is very poor?

It seems to be usually when the larger AP WUs are added to the download mix that things get rather tied up. I have noticed at times that it appears that AP downloads, although still slow, seem to be less likely to stall or hang, thus tying up the download link longer.

Some random thoughts in the evening..

.. are AP and MB work units generated on some machine and then copied over network to a distribution server?

If so, are they loaded to the downlod server using the same network card/interface that is used by users to download work units to their machines?

if so, could it be that the generator/copier saturates the channel?

if not so, how about the disk read/write speed of the download machine? Simultaneous red/write operations could hurt RAID performance. The writes alone are quite costly.

But I guess that you have ruled these out already.
____________

Some random thoughts in the evening..

.. are AP and MB work units generated on some machine and then copied over network to a distribution server?

If so, are they loaded to the download server using the same network card/interface that is used by users to download work units to their machines?

if so, could it be that the generator/copier saturates the channel?

if not so, how about the disk read/write speed of the download machine? Simultaneous red/write operations could hurt RAID performance. The writes alone are quite costly.

But I guess that you have ruled these out already.

Can someone recommend a good reliable source to get a paid proxy that would work with SETI?

Few weeks already my main host is almost constantly out of work from SETI.
BOINC big download backofs make impossible to fill cache.
Only when I have time to constantly press "retry now" I can fill cache for day or 2 and usually only for GPU, CPU remains empty/on backup project.
____________
News about SETI opt app releases: https://twitter.com/Raistmer

Been not watching closely over the traditional Australia Day long weekend chaos, and my machines were crunching when I looked occasionally. If I had stuck transfers I just put this retryMainTransfers.cmd in my scheduled tasks for every 20 mins or so:

Been not watching closely over the traditional Australia Day long weekend chaos, and my machines were crunching when I looked occasionally. If I had stuck transfers I just put this retryMainTransfers.cmd in my scheduled tasks for every 20 mins or so:

@ECHO OFF boinccmd --get_file_transfers > mainxfers.txt FOR /F "tokens=1,2" %%i IN (mainxfers.txt) DO ( IF "%%i" EQU "name:" echo %%j IF "%%i" EQU "name:" boinccmd --file_transfer http://setiathome.berkeley.edu/ %%j retry )

I have something very similar to this for the same purpose. Gotta love DOS programming.

____________

Dip in traffic towards Seti detected?
Yes, definitely a downturn. Expect failing reports after a good day of rapid access.

[edit] The thin blue line has hit the bottom - no more reporting until later, I fear. [end edit]