Funny how it works so well with certain Proxies...

I finally just decided to try some proxies. After 5-10 of them failed and wouldn't work, I found one that did. They're "screaming" along now at 6-7KB/sec now with very few time-outs. Weird. I've never had issues before, nor have I ever needed to use a proxy.

For those wondering.. at least in the US anyway..

2013-01-16 16:23:10 Using HTTP proxy 72.64.146.136:8080


edit: starting to see messages I was starting to think I would never see..

2013-01-16 16:34:05 SETI@home Finished download of ap_24ap12ab_B5_P1_00331_20130113_17804.wu
2013-01-16 16:35:29 SETI@home Finished download of ap_24ap12ab_B6_P0_00063_20130113_22569.wu
2013-01-16 16:35:35 SETI@home Finished download of ap_24ap12ab_B5_P1_00116_20130113_17804.wu
2013-01-16 16:36:24 SETI@home Finished download of ap_24ap12ab_B5_P0_00363_20130113_11783.wu
2013-01-16 16:37:29 SETI@home Finished download of ap_24ap12ab_B6_P0_00061_20130113_22569.wu

edit2: One of the downloads hadn't started yet at all with all the back-offs before starting to use a proxy, and start-to-finish was 16 minutes.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

This is the only project that I know of that places so much demand on the sanity of a human mind.
My RAC is like a yo-yo and now the biggest problem is keeping download units downloading.
A proxy server again is needed to maintain a download without it timing out.

We must be nuts to keep going on Seti but here we are. I am starting to talk to myself just a bit too much. MSattler has the right idea. The kitties prevent insanity. I think...... Who knows eh!!

Well you know they say the definition of insanity is doing the same thing multiple times expecting a different result. By that definition, we are definitely insane by sticking around expecting things to be different each time. :p

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

YUP

I wunderz why the Master Database iz `only` geting 415 queries per second,
It seems a bit low for a fully working system :)

I was hoping by now things would be a little more normal, however downloads are still barely happening.
Although at least there arent' any Scheduler request errors or timeouts at the moment.

---

Grant
Darwin NT

Wow I am really jealous! My AP are averaging of 40 retries and 3-5 hours to download. What is you ISP and where are you located?

---

Wow I am really jealous! My AP are averaging of 40 retries and 3-5 hours to download. What is you ISP and where are you located?

They appear to be in the wonderful Great Britain, and as we have noticed with connection issues in the past, the path in which your requests go through the Internet to reach the servers seems to make a difference. Hence why the use of proxies helps with more stable communications than not using one.

I myself have never had an issue with connecting, save for the occasional time-out here and there, but nothing long-term, and nothing too detrimental. When others were complaining about having hundreds of DLs that just would not go, I had no problem getting 10+ APs to go through usually on the first try, and at 40-50KB/sec at that.

As of late though, what I have experienced in the past is no longer happening for me. I get endless time-outs/stalls/errors. I just end up pulling up the proxy list and filter it to US and start at the top and work my way down the HTTP/S proxies until I find one that works. Once all the DLs are done, I go back to no proxy as I was having scheduler contact issues whilst using a proxy yesterday (most notably, HTTP error 417).

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I wunderz why the Master Database iz `only` geting 415 queries per second,
It seems a bit low for a fully working system :)

Ok, so who did what, now it`s 2704
Now that iz a pile up.

And back to a more normal 800ish.




I will shoulder some of the blame for the current problems - I'm trying to commission a new cruncher, so am attempting to load all the various bits and apps, then probably hit the servers for a full load of tasks....

---

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

OH so its your fault it took me 24 hours to download a stupid AP!

---

[/quote]

Old James

No, I only started a couple of hours ago - but I will take the blame for thinking about it...
The actual start time was 17:28gmt - and I'm still waiting for the applications to find their way out of the maze...


I've just started running an alternative project on the new cruncher (Malaria control) just to see how fast it is...

---

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

Been a few dips in inbound traffic over the last few hours, but doesn't appear to have had an effect on my systems. Downloads still abysmal- only difference between now & just after the outage is i don't have to keep suspending & re-enabling network access. Best download speed i've notcied since the outage is 5kB/s. Usually it's less than 2kB/s; 10-20min for a MB WU seems to be the going rate.

---

Grant
Darwin NT

Been a few dips in inbound traffic over the last few hours, but doesn't appear to have had an effect on my systems. Downloads still abysmal- only difference between now & just after the outage is i don't have to keep suspending & re-enabling network access. Best download speed i've notcied since the outage is 5kB/s. Usually it's less than 2kB/s; 10-20min for a MB WU seems to be the going rate.

Its down right ridiculus. A few days ago when I had a lightning fast .85KBS speed it took me 16 hours to force an AP work unit to download.
today im getting 8kbs and the AP work is gagging and pukeing the whole download.
I cant see buying two new servers if the pipe keeps getting plugged up.
I have 71 time outs on the I7 920. Its aggravating I tell ya, Very aggravating. Ok rant over back to abuseing the retry button:)

---

[/quote]

Old James

I cant see buying two new servers if the pipe keeps getting plugged up.

The pipe has been plugged up for years, so the present issues are either due to the download servers, or some other internal network issues IMHO.
The fact the network is saturated doesn't help, of course.

---

Grant
Darwin NT

I find it very strange that, with the pipeline at/near saturation one server manages to shuffle work out at an acceptable rate while the other crawls (at best). The number of re-tries generated by the crawling server cannot help the overall through put, thus adds to the general pipeline clog, which in part will be down to the re-try requests and associated traffic.
Wasn't there a short period a few months back when only the "speedy" server in action, and if I recall there were far fewer re-try events at that time?

---

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

My MB Cuda caches contain mostly Shorties.

They're back...

132 out of 200 task are shorties here(AR > 2.2). Bad part is, most of them are for CPU, which is more inefficient than GPU with them (1.5 minutes for GPU vs 12-15 minutes CPU. In contrast, WUs with middle AR, are 7-8 minutes on GPU and 45-55 min on CPU. Huge difference between two groups of units).
I usually rescheduled them before, but someone woudlnt be happy with the given credits, so I stopped doing so.

As for AP download, only proxies helped me to fill my cache. I even lowered it, bcs there was a moment with 100+ APs. My puny 5770 can do like 12-13 APs for a day(for 16-17 hours).

---

I have APs that are choking and gagging for the last 8 Hours. They are at 96% to being downloaded so mabye only 3 more hours:)

---

[/quote]

Old James

I use a proxy and my APs take about 12 minutes to download from start to finish with no time-outs/stalls.

My single-core MB-only machine is just on its own and manages to get MBs just fine with only 2-3 re-tries. Main cruncher is getting 6-8 APs/day and they have to be nudged along and assisted the whole way.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)