Cache Architecture
The original architectural documents for Traffic Server were lost in the transition to an open source project. The documents in this section are provisional and were written based on the existing code. The purpose is to have a high level description of aspects of Traffic Server to better inform ongoing work.
In the final section on “hacking” we try to document our approaches to understanding and modifying the source.
- Cache Architecture
- Cache Initialization
- Core Cache
- Data Structures
STORE_BLOCK_SIZECacheHostTableCacheHostResultCacheHostRecordOpenDirCacheVCHttpTunnelCacheControlResultCacheHTTPInfoVectorHTTPInfoCacheHTTPInfoHTTPCacheAltStripeStripeSMPreservationTableDocDiskHeaderDiskStripeBlockStripeHeaderFooterDiskStripeBlockQueueDiskStripeCacheTypeCacheVolConfigVolConfigVolumesCryptoHashCache
- API functions
- Topics to be done
- Cache Consistency
- Volume Tagging
- RAM Cache
- Shared-Memory Cache Directory (Fast Restart)
- Motivation
- Design principles
- Object layout
- Startup
- Per-stripe attach and the fast path
- Storage changes and partial attach
- Shutdown
- Crash and recovery summary
- Huge pages
- Concurrency model
- Disabling the feature: stale-segment purge
- Operator tooling:
traffic_ctl cache shm - Configuration
- Platform considerations
- Testing
- Limitations and non-goals
- Source map
- Cache Tool
- Tiered Storage