...
Being able to throttle HTTP streams can be a valuable function for reducing bandwidth waste. TBD more details, Alan.
The following configurations have been added to control this feature (the default values are shown):
Code Block |
---|
CONFIG proxy.config.http.flow_control.enabled INT 0
CONFIG proxy.config.http.flow_control.high_water INT 0
CONFIG proxy.config.http.flow_control.low_water INT 0
|
CPU thread affinity
It is now possible to set thread affinity for the main worker threads. This can improve performance, particular on NUMA systems. This is configured via
Code Block |
---|
CONFIG proxy.config.exec_thread.affinity INT 1 |
Removed configurations
Delay proxy services until cache is enabled
When Traffic Server starts, we load meta-data information from the cache. For very large caches, this can take a fairly long time (several seconds). During this load and initialization time, the server will by default proxy requests to the origin. A new configuration has been added, which prevents proxying while the cache is being initialized:
Code Block |
---|
CONFIG proxy.config.http.wait_for_cache INT 1
|
Controlling chunking size
A new configuration option is added, which lets you control the size of the chunk sizes for content that is Transfer-Encoding with chunking (default value shown):The following configurations are no longer supported (or necessary). They should be removed from your records.config if you have them in there.
Code Block |
---|
CONFIG proxy.config.http.bandwidth_mgmtchunking.filenamesize STRINGINT "" 4096 |
New Plugin: cacheurl
TBD: More details.
...