Page History

...

NOTE: My goal here is to give myself the most pretty aggressive caching at the highest throughput possible.

...

From Leif H: "This recommendation is wrong, it should be set to 0.0 for it to always kick in. It allows the server to continue fetching / caching a large object even if the client disconnects. This setting (with a value of 0.0) is a prerequisite for getting read-while-writer to kick in."

I've since updated this setting.

CONFIG proxy.config.http.background_fill_completed_threshold FLOAT 0.000000

...

The default config for ATS specifies that the proxy itself use data "chunks" of 4KB each.
Being that I'm on a
high-speed Internet link at home, I decided to increase this. I originally went with 64KB, only to find my
Internet Radio seemed to be having problems. 16KB should remedy that
I'm currently using a setting of 64KB. If you find yourself annoyed with how long
streaming Internet Radio takes when rebuffering, try setting this to 16KB instead.

From what I understand it's a balancing act between what Internet Radio will accept,
and throughput of the cache overall.

CONFIG proxy.config.http.chunking.size INT 16K64K

HTTP Connection Timeouts

I decided to use Mozilla Firefox's values here, along with one of my own.
It turns out proxy.config.http.transaction_active_timeout_in was essentially shutting down my
streaming Internet Radio connections. I increased that setting from 15 minutes to 12 hours.

...

I'm sure I have experienced higher latency, but also somehow avoided a disk contention problem.

P.S. Since testing this explicitly, Microsoft Bing has done some backend work that has improved HTTP responses.
I currently believe this setting only really matters when TCP retries come into play.

CONFIG proxy.config.cache.mutex_retry_delay INT 25

...