Netsurf 3.3 disc cache problems

which surely implies that a disc cache would be beneficial and that NetSurf’s method of calculating how fast (or slow) it is . . . is faulty.

You know where the source is

The only reason the “stop caching to disc, it’s too slow” speed check was added was because RISC OS users reported the slow writes problem. Their desktops were grinding to a halt making e.g. dragging another window about or typing jerky and unresponsive. RISC OS single tasks during writes, and if you visit a page you may suddenly have 30 little thumbnails to cache, half a MB of CSS, a few hundred kB of HTML, and a 1MB JPEG to put on an SD card. With such an operating system… its not pleasant.

The benchmark values you quote are irrelevant to real-world data usage patterns. Also, nobody cares if a benchmark tool makes things slow and unresponsive for a while. But for a browser? We have to be a little more civilised.