You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 115 Next »

While the default configuration values for ATS will get you up and running, they're somewhat designed for regression testing and not real-world applications.

This page documents what I've discovered myself through a fair amount of experimentation and real-world experience.

The following lists the steps involved in taking a generic configuration, and modifying it for my own needs. Yours may vary, however, and I'll do my best
to indicate which settings should be sized based on your install.

Please keep in mind the following only applies to creating a forward-only web proxy caching setup.

The following lists steps involved in taking a generic Traffic Server install and customizing it for my own needs.

NOTE:  Please use the following with Apache Traffic Server v5.0.0 and higher.

 Home Machine

  • Make/Model: Apple iMac Mid 2011
  • CPU: 3.4 Ghz Intel Core i7 (quad-core w/Hyperthreading)
  • Memory: 16GB
  • Disk: 1TB
  • OS: Mac OS X v10.9.3
  • Cache Size: 8GB
  • Browser: Google Chrome v35

Testing Regimen

The following settings have been tested against the following:

  • IPv4 websites
  • IPv6 websites
  • Explicitly difficult web pages (i.e. Bing Image Search)
  • Explicitly SSL web sites (i.e. Facebook)
  • Internet Radio (HTTP streaming, as well as iTunes Radio & Pandora)

The following settings are all located in /usr/local/etc/trafficserver/records.config.

Since Traffic Server v5.0.0 has reorganized this file, I'll go through the relevant sections here.  When adding configurations, simply add the settings below the existing ones.

Thread Configuration

As I'm using Traffic Server on a personal basis, I decided to explicitly configure it to not consume as many CPU cores as it might do otherwise.

If your situation is different, simply change proxy.config.exec_thread.limit to set how many CPU cores you'd like to use.

CONFIG proxy.config.exec_thread.autoconfig INT 0
CONFIG proxy.config.exec_thread.limit INT 1

HTTP Connection Timeouts

I'm using Traffic Server on a pretty speedy broadband connection.  As such, I've configured it to be somewhat impatient in terms of timeouts.

CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 600
CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 600
CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 30
CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 30
CONFIG proxy.config.http.transaction_active_timeout_in INT 43200
CONFIG proxy.config.http.transaction_active_timeout_out INT 43200
CONFIG proxy.config.http.accept_no_activity_timeout INT 30
CONFIG proxy.config.net.default_inactivity_timeout INT 30

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 few extra connections open for additional requests speeds things up.

The third setting controls how often Traffic Server will internally poll to process network events.  As I'm on a machine that can't easily handle 2-3% CPU load constantly, I reduced this.

CONFIG proxy.config.http.origin_max_connections INT 32
CONFIG proxy.config.http.origin_min_keep_alive_connections INT 2
CONFIG proxy.config.net.poll_timeout INT 50

Cache Control

The following configurations tell Traffic Server to be more aggressive than it would otherwise, with regard to caching overall as well as some speed-ups.

Also, I found that from a correctness point of view, my cache behaves better when not caching "dynamic" URLs.

CONFIG proxy.config.http.cache.cache_urls_that_look_dynamic INT 0
CONFIG proxy.config.http.chunking.size INT 128K
CONFIG proxy.config.http.server_session_sharing.match STRING host
CONFIG proxy.config.http.cache.ignore_server_no_cache INT 1

Heuristic Cache Expiration

The default config for Traffic Server specifies that after 1 day(86,400 seconds), any object without a specific expiration cannot be cached.

I'd prefer that they stick around for between 1-3 months. 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 to keep objects in the cache, using Traffic Server's built-in heuristics.

CONFIG proxy.config.http.cache.heuristic_min_lifetime INT 2592000
CONFIG proxy.config.http.cache.heuristic_max_lifetime INT 7776000
CONFIG proxy.config.http.cache.heuristic_lm_factor FLOAT 0.75

Network Configuration

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

I decided for my purposes that's pretty excessive.

CONFIG proxy.config.net.connections_throttle INT 2K

RAM And Disk Cache Configuration

The default config for Traffic Server specifies a few things here that can be tuned.

First, I decided to explicitly set my RAM cache settings.  If your situation is different, simply change proxy.config.ram_cache.size to set how much RAM you'd like to use.

Second, I observed my cache running via the "traffic_top" utility and have set the average object size accordingly.

NOTE:  One should always halve the setting for that configuration, as it allows "headroom" within Traffic Server such that one will never run out of slots in which to store objects.

Third, I've explicitly tuned the average disk fragment setting as well as disabled a feature that for me slows down the cache a bit.

NOTE:  These settings require one to refresh the disk cache to take effect.  Simply remove /usr/local/var/trafficserver/cache.db and restart Traffic Server to refresh the disk cache.

CONFIG proxy.config.cache.ram_cache.size INT 64M
CONFIG proxy.config.cache.ram_cache_cutoff INT 8M
CONFIG proxy.config.cache.min_average_object_size INT 64K
CONFIG proxy.config.cache.target_fragment_size INT 262144
CONFIG proxy.config.cache.mutex_retry_delay INT 10
CONFIG proxy.config.cache.enable_read_while_writer INT 0

Logging Configuration

The defaults for Traffic Server specify a squid-compatible logfile that's binary in nature.  I prefer to have the file readable so I'm overriding this.

CONFIG proxy.config.log.squid_log_is_ascii INT 1

HostDB Configuration

The defaults for Traffic Server configure the disk-based DNS cache to be rather large.  First, I found I got a decent speed improvement by sizing this down.

Second, I specifically prefer IPv6 over IPv4.  This simply tells the cache to prefer the newer IPv6 when possible.

Third, I also allow the cache to use stale DNS records for up to 5 minutes while they're being updated.  This also contributes to cache speed.

If your situation is different, simply get to know the following settings.  It takes a bit of practice to get used to, but they're all tunable.

##############################################################################
# HostDB
##############################################################################
CONFIG proxy.config.hostdb.ip_resolve STRING ipv6;ipv4
CONFIG proxy.config.hostdb.size INT 64K
CONFIG proxy.config.hostdb.storage_size INT 16M
CONFIG proxy.config.hostdb.serve_stale_for INT 300

Restart Traffic Server

Once you've updated the relevant records.config settings, simply refresh your disk cache if necessary and then restart Traffic Server.

After that's been done, enjoy your newly-tuned proxy server.

sudo /usr/local/bin/trafficserver stop
sudo /usr/local/bin/trafficserver start

 

Previous Page:  WebProxyCacheSetup

Next Page: WebProxyCacheBrowser

  • No labels