Very slow transfers from NAS to Titanium

You can also install pi-hole to block Ads to speed things up a bit.

On the subject of Pi-Hole.

1. The DHCP server in that build is almost certainly better than the router offering most people have.
2. The DNS Server offering is almost certainly better than the router offering most people have.

Item 1 might deal with many of the problems with DHCP timeout discussed elsewhere.
Item 2 is likely to improve browsing speed because of the DNS caching, feature/content rich pages engender a lot of DNS queries and every millisecond counts when you get enough queries.

Finally the front page aspect of Pi-hole is the advert and tracker filtering provided by the main Pi-hole software. Less crap unwanted material downloading so things are faster and the whizz-bang feature ads probably don’t even render properly on a RO browser anyway

Setting ECPFlowControl to None fixed the problem with the link not establishing with ECPAdvertise set to 1000

I did wonder about that one. I assumed the on status was a Titanium supplier recommendation.
Back when I regularly did desktop stuff I used to turn off the flow control on PC NICs.

Fortunately the elderly status of the RO stack means we don’t have to worry about people running a dual (IPv4/IPv6) stack setup. Dual stack is always bad. One or the other folks if you want speed.

changed my setting from 1000 to 100 and i now get an average 40 to 50 kbs transfer speed on my internet downloads which is a lot better than 4 to 5 kbs so result i would say.

Hmmm…

When MangaReader is having a good day, or downloading something from a decent server in NetSurf, my Pi2 (still RISC OS 5.23) connected to the internet via a NetGear FS205 switch connected to a Vonets VAP11G WiFi thingy…

…can manage around 250Kbytes/sec, which is about half of what my ~3-4Mbit link is capable of, but possibly slightly laggy due to the number of steps involved, poor signal, etc.

I did the same test on the Titanium running under Debian buster.

Downloads using wget average about 48MB/s compared to 2.5MB/s using RISC OS..

Normally NetSurf on the Titanium downloads to a maximum of 700KiB/s. On the RISC OS Linux port on the RPi4 NetSurf managed 4MiB/s but RO stiffed shortly after.

The RISC OS network stack doesn’t like high latency networks. Downloads can be a lot slower than the maximum bandwidth available. A work around is to use a proxy server.

With Privoxy installed on an RPi3B+ NetSurf on the Titanium can now download at 2MiB/s.

This RPi3B+ already has pi-hole on it and provides a small amount of network attached storage with a share.

@Chris, thanks for two good tips, pi-hole & the proxy.

4 megabytes per second is quite reasonable.

loaded privoxy on a pi4 am using it now and it is like winning the lotto i can now down load the backdrop images in 3:24 mins great over 900kbs

I have been having problems with my Titanium and very slow network performance. I noticed it when !Safestore was running saving to a Windows Server 2016 Enterprise machine with a RAID 6 array as storage (1 × 12.7TB and 1 × 27.2 TB arrays). It was taking minuets to save the individual larger files.
I tried many of the settings mentioned earlier in this thread, but to no avail.
The only thing that I had changed recently (probably months ago) was that my whole network infrastructure had been changed to Ubiquiti hardware ( 1 × 48 way switch, 1 × 48 way POE, 2 × 8 way POE, 1 × 8 way switch and 1 x USG Pro-4 router).
As a last resort, I added back one of my old Netgear 8 way switches (POE powered) and plugged in the Titanium.
!Safestore has just saved over 13 thousand files in the time to write this message…

Just to note regards the previous message, ShareFS was also slow when moving files to any running RISCOS machine (Pi, Beagle or OMAP5).
(Also now over 30 thousand files…)

Ubiquiti hardware

Managed switches so you should be able to a CLI command like show port all, or show port 1 (if I’ve got the syntax right) to see what the operational mode for port 1 is.

Check the duplex and speed settings it ends up at.

Doing a speed auto 1000 should set it to auto-negotiate duplex and give 1000 full on a capable device, speed auto 100 same thing for 100Mb.

Check also what the current status is of the port the Netgear connects to.