1 / 34

Apache Traffic Server

Apache Traffic Server. HTTP Proxy Server on the Edge Leif Hedstrom Engineer leif@yahoo-inc.com zwoop@apache.org. Agenda. History and background of Traffic Server Brief introduction to HTTP intermediaries Concurrency problems (and solutions) Choosing an intermediary Building a CDN

ketan
Télécharger la présentation

Apache Traffic Server

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Apache Traffic Server • HTTP Proxy Server on the Edge • Leif Hedstrom • Engineer • leif@yahoo-inc.com • zwoop@apache.org

  2. Agenda • History and background of Traffic Server • Brief introduction to HTTP intermediaries • Concurrency problems (and solutions) • Choosing an intermediary • Building a CDN • TCP connection management • Server Load Balancer (if time permits)

  3. Origins of the software

  4. Open Source benefits

  5. Forward Proxy

  6. Reverse Proxy

  7. Intercepting Proxy

  8. The concurrency problem

  9. Solution 1: Multithreading

  10. Problems with multi-threading

  11. Solution 2: Event Processing

  12. Problems with event processors

  13. Traffic Server threads model

  14. Plenty of FOSS Proxy Servers

  15. Choosing an intermediary

  16. SMP Scalability and performance

  17. Traffic Server performance • 350,000 requests / sec in production CDN • 30 Gbps / second • Max capacity is at least 10x normal usage, to deal with massive spikes. • 85,000 requests / sec with small content out of cache, for a single (lab)box • 3.6Gbps out of a single box, with larger content (4x GigE NIC bonded) (all numbers from Y! CDN and lab testing).

  18. HTTP/1.1 Features

  19. Ease of use, extensible

  20. Traffic Server making Ops easy • Traffic Server will restart automatically if it crashes • Traffic Server will kill itself if it isn’t responding • Traffic Server can reload most configurations without server restarts • Adding plugins is a matter of dropping in the shared object, and restarting • Stats and configurations are accessible via command line utilities

  21. Example evaluation sheet

  22. Operations is important!

  23. Yahoo! Traffic Server Use Cases

  24. Content Delivery Network

  25. CDN on the Edge

  26. Traffic Server CDN configuration CONFIG proxy.config.http.server_port INT 80CONFIG proxy.config.cache.ram_cache.size INT 512MB CONFIG proxy.config.url_remap.remap_required INT 1 map http://cdn.example.com/js http://js.example.com reverse_map http://js.example.com http://cdn.example.com/js map http://cdn.example.com/css http://css.example.com reverse_map http://css.example.com http://cdn.exampe.com/css map http://cdn.example.com/img http://img.example.com reverse_map http://img.example.com http://cdn.example.com/img /dev/sd2

  27. Common enemies of performance

  28. TCP 3-way Handshake

  29. Congestion avoidance

  30. TCP Connection Management

  31. Why Server Load Balancers?

  32. Server Load Balancer

  33. Executive Summary • Understand your requirements • Evaluate available solutions • Building a CDN is easy • Apache Traffic Server is • Fast and SMP scalable • HTTP/1.1 compliant • Battle hardened • Easy to configure and operate • Actively developed • Free as in beer

  34. trafficserver.apache.org

More Related