...

While the default ATS options for this may be optimal under heavy load,
I found using the simpler LRU algorithm much faster and more useful.

The following specifies 768MB 256MB of RAM cache, with objects of up to 128MB 64MB in size,
to be managed using LRU. During normal use, RAM utilization should rise and rise
until all 768MB 256MB is used, then the LRU algorithm should kick in. Also,
figure on at least 100MB of general RAM overhead for ATS in addition to this.

CONFIG proxy.config.cache.ram_cache.size INT 768M256M
CONFIG proxy.config.cache.ram_cache_cutoff INT 128M64M
CONFIG proxy.config.cache.ram_cache.algorithm INT 1
CONFIG proxy.config.cache.ram_cache.use_seen_filter INT 01

NOTE: This setting should be sized relative to the amount of memory you want to use.
Also, it requires restarting ATS to properly take effect.

...

The default config for ATS leaves these disabled. I believe these to be somewhat useful
enables some buffering between ATS and the client.  While I believe some inbound buffering to be useful for HTTP streaming applications such as Internet Radio and YouTube. However,
setting these too large tends to slow down the cache overall.

...

, I've had some memory issues with this.  For now, I'm leaving these disabled.

{code}
CONFIG proxy.config.net.sock_send_buffer_size_in INT 0
CONFIG proxy.config.net.sock_recv_buffer_size_in INT 0
CONFIG proxy.config.net.sock_send_buffer_size_out INT 0
CONFIG proxy.config.net.sock_recv_buffer_size_out INT 

...

0
{code} 

Step 3 – Secure

Maximum Inbound Concurrent Connections

...