After months, I just tried Folding@Home, and it's desolate. [poor Internet uplink at home]

[TennesseeTony]

Earlier today, they actually fixed the broken cable. My home is now back on the 'net. And the network in which I am located is even permitted to access FreeDC and EOC. :-)

And....is Folding@Home still desolate? Do you still have to use wondershaper?

 

[Markfw]

not sure what you mean by desolate. I have gone way down in my points to do trying to dave money, but it looks fine to me:

 

[StefanR5R]

Do you still have to use wondershaper?

Maybe, maybe not.

Earlier today I tested https://speed.cloudflare.com/ first without wondershaper, and it gave much better values than those I showed in post #9. The summary said "Video Streaming: Good • Online Gaming: Average • Video Chatting: Good", I think. (I did this on a PC with OpenSuse Linux though, not on one of my F@H computers which have Linux Mint.) Then I enabled wondershaper, and that gave even lower latencies and jitter and was summarized as "Video Streaming: Great • Online Gaming: Great • Video Chatting: Great".

I'll have yet to try F@H.

Edit:
I also visited the cable modem's diagnostic pages now.
https://192.168.100.1/RgConnect.asp shows quite many correctable errors, like before the damage+repair. I don't know if the error rate is the same or lower now. There are no uncorrectable errors.
https://192.168.100.1/RgEventLog.asp doesn't show any connection loss (with or without automatic reconnection) for the entire three days since the cable was repaired. Which is good and seems better than before.

 

[Skillz]

Correctable errors are bad, but not that bad. Its the uncorrectable ones that do the most damage.

One thing that can cause errors like that is from bad cable or too many splitters. Also if you have any exposed splitters or lines that don't have terminators covering them can cause it as well.
Though I would think the likely reason, being that you live in an apartment type complex is that their are too many splitters on your line causing errors.

What do the power numbers look like and the SNR? Too much power (using amps on the line) or not enough power (usually from the line being too long or split too many times) can cause errors also.

Screenshot for you to reference off of from my own cable modem with good power, good SNR and no errors.

 

[StefanR5R]

My Pwr and SNR values are lower, but still acceptable according to this page:
speedguide.net: What cable modem signal levels are considered good?

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256		714000000 Hz	2.3 dBmV	39.7 dB	14172	0
2	Locked	QAM256		618000000 Hz	2.5 dBmV	40.2 dB	7647	0
3	Locked	QAM256		650000000 Hz	2.3 dBmV	40.1 dB	4763	0
4	Locked	QAM256		658000000 Hz	2.9 dBmV	40.1 dB	3717	0
5	Locked	QAM256		674000000 Hz	3.4 dBmV	38.6 dB	9024	0
6	Locked	QAM256		682000000 Hz	2.8 dBmV	39.9 dB	9624	0
7	Locked	QAM256		690000000 Hz	2.1 dBmV	39.8 dB	10701	0
8	Locked	QAM256		698000000 Hz	2.7 dBmV	39.8 dB	11009	0
9	Locked	QAM256		626000000 Hz	3.2 dBmV	40.2 dB	7092	0
10	Locked	QAM256		634000000 Hz	3.1 dBmV	40.2 dB	6409	0
11	Locked	QAM256		642000000 Hz	2.9 dBmV	40.1 dB	6338	0
12	Locked	QAM256		666000000 Hz	3.5 dBmV	40.1 dB	4479	0
13	Locked	QAM256		746000000 Hz	3.3 dBmV	39.5 dB	13561	0
14	Locked	QAM256		754000000 Hz	3.2 dBmV	39.4 dB	13024	0
15	Locked	QAM256		762000000 Hz	3.3 dBmV	39.3 dB	11534	0
16	Locked	QAM256		770000000 Hz	3.2 dBmV	39.3 dB	9912	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1		ATDMA		5120 Ksym/sec	35400000 Hz	44.8 dBmV
2		ATDMA		5120 Ksym/sec	41800000 Hz	44.5 dBmV
3		ATDMA		5120 Ksym/sec	48200000 Hz	44.8 dBmV
4		ATDMA		5120 Ksym/sec	61000000 Hz	44.8 dBmV

 

[Skillz]

I dont think that amount of correctable errors is a cause for any kind of concern. It looks like a lot, but I don't think it actually is a lot.

 

[StefanR5R]

Yes, I am guessing that the cause for transfer failures of large F@H/BOINC result files is (or has been) bad TCP/IP packet queuing by the cable modem-router or a router at the ISP, coupled with upstream routers of 3rd parties eventually not tolerating the huge latencies when the routes are respectively long.

Physical layer problems or maybe just plain overbooking manifested as my other problem: Actual connection losses between cable modem and whatever sits upstream, which sometimes didn't happen for months and sometimes happened several times a day especially on weekends — most of the time followed by automatic reconnect, sometimes (generally at most inconvenient times) followed by the modem just doing nothing about it until I reset it.

Anyhow. Now that the required ducts have been laid in our street, I hope that fiber is threaded in sooner than later, and that the apartments in our house finally get FTTH...