Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changing cache size, as well as object expiration settings.

...

  • Server Host: Vultr (www.vultr.com)
  • CPU: 3.6 Ghz Intel CPU (dual core)
  • Memory: 2GB
  • Disk: 40GB SSD
  • OS: CentOS Linux 7.0
  • Cache Size: 2GB1GB
  • Browser: Google Chrome v39v40

Testing Regimen

The following settings have been tested against the following:

...

Code Block
CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 300
CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 300
CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 10
CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 10
CONFIG proxy.config.http.transaction_active_timeout_in INT 14400
CONFIG proxy.config.http.transaction_active_timeout_out INT 14400
CONFIG proxy.config.http.accept_no_activity_timeout INT 10
CONFIG proxy.config.net.default_inactivity_timeout INT 10

Origin Server Connect Attempts

I had a similar experience tuning Squid in this regard.  This first setting controls how many connections ATS can make outbound to various Internet servers,
on a per-server basis. The default allows for unlimited connections, and while that may be useful on a heavily loaded server I find that it actually slows things down a bit.

I decided to go with 32 connections per origin server simultaneously.  I also found keeping a connection open for additional requests speeds things up.

Network Events Polling

This The third setting controls how often Traffic Server will internally poll to process network events.  Even though I'm now on a machine that can handle 2-3% CPU load, I reduced decided to reduce this.

 I haven't noticed any significant performance difference as a result of this.

Code Block
CONFIG proxy.config.http.origin_max_connections INT 32
CONFIG proxy.config.http.origin_min_keep_alive_connections INT 1
CONFIG proxy.config.net.poll_timeout INT 50

Cache Control

...

I'd prefer that they stick around for between 1-3 months4 weeks. This setting is contentious in that what it should be is debatable.

The goal here is to enforce a window of between 1 and 3 months 4 weeks to keep objects in the cache, using Traffic Server's built-in heuristics.

Code Block
CONFIG proxy.config.http.cache.heuristic_min_lifetime INT 2592000604800
CONFIG proxy.config.http.cache.heuristic_max_lifetime INT 77760002592000

Network Configuration

The default config for Traffic Server allows for up to 30,000 simultaneous connections.

...