Configuring Apache Servers for Better Web Perormance
•Télécharger en tant que PPT, PDF•
2 j'aime•6,216 vues
Apache is the most popular web server in the world, yet its default configuration can't handle high traffic. Learn how to setup Apache for high performance sites and leverage many of its available modules to deliver a faster web experience for your users. Discover how Apache can max out a 1 Gbps NIC and how to serve over 140,000 pages per minute with a small Apache cluster. This presentation was given by Spark::red's founding partner Devon Hillard in March 2012 at the Boston Web Performance Meetup.
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Configuring Apache Servers for Better Web Perormance
Similaire à Configuring Apache Servers for Better Web Perormance (20)
Dernier
Dernier (20)
Configuring Apache Servers for Better Web Perormance
- 1. Apache Web Performan ce Leveraging Apache to make your site fly
- 2. Who am I? & Why would you listen to me? Why would you listen to me? Why would you listen to me?
- 3. Devon Hillard Web Application Architect Built 10MinuteMail Run Spark::red, an enterprise eCommerce Hosting company Complex Web Apps with extremely high traffic and critical performance needs devon@sparkred.com
- 5. • Traffic Capacity • Request handling speed • Request handling throughput • Lower CPU/memory/bandwidt h usage • Scalability
- 6. • Page Load Time • First draw • Inter-actable • Complete • Page Interaction Responsiveness • Time to Complete Use Case
- 7. These two are TIED • Browser caching of static assets reduces page load time AND reduces the number of requests the server has to handle for the same number of page views • AJAX requests can typically be handled with far fewer resources than full page requests • Reduced asset sizes means less bandwidth used and shorter request response sending times • Solving for the Client brings Server performance gains!
- 8. Why Should I Care?
- 9. Everyone Wins! • Client-Side Performance means • happier users • increased conversions • increased SEO ranking • Server-Side Performance means • more capacity on same hardware • saves money • scaling is easier
- 10. Increased Conversions •+100 ms of page load time = 1% drop in sales •+500 ms of page load time = 20% drop in searches •+400 ms of page load time = 5-9% increase in clicking “back” button before the page finished loading
- 11. Why Apache?
- 12. Why I Use Apache • Popular web server - it’s everywhere • Easy to install, troubleshoot, and find information on • Mature and stable • Lots of extensions • Enterprise support requirements • It Is fast enough to max out your hardware!
- 13. CPU Util @ 930 Mbit/sechttp://www.webperformance.com/load-testing/blog/2011/11/what-is-the-fastest- webserver/
- 14. PCA Awards • Saw 4x the planned for traffic during spikes • 140,000+ pages/minute - 2,333 pps (2012) • 3,000+ Mbit/sec (2011) • 1,200+ Mbit/sec PLUS Akamai CDN offloaded traffic (2012) • The site stayed up and was quick to load and responsive to interact with the whole time iftop output - 613 Mbit/sec
- 15. Puppies
- 18. Which MPM? • Worker MPM scales for high traffic without running out of memory better • Less time spent tuning worker configs • Unless you’re still using non-threadsafe Apache code (some PHP, etc..) • New in Apache 2.4 is the Event MPM
- 19. Default <IfModule worker.c> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0</IfModule> Mine <IfModule worker.c> ThreadLimit 100 StartServers 5 MaxClients 5500 ServerLimit 200 MinSpareThreads 100 MaxSpareThreads 1000 ThreadsPerChild 100 MaxRequestsPerChild 0</IfModule> MPM Worker Configs
- 20. ab with small file Version Apache 2.2.3 MPM Worker Document Size 119 bytes Concurrency Level 1,000 Total Requests 100,000 Requests Per Second 20,790 r/s Throughput 8,077 kb/s hex core X5675
- 21. ab with large file Version Apache 2.2.3 MPM Worker Document Size 95,002 bytes Concurrency Level 1,000 Total Requests 100,000 Requests Per Second 1,258 r/s Throughput 119,966 kb/s hex core X5675
- 22. Linux Kernel Configs net.ipv4.tcp_max_syn_backlog=30000 net.core.netdev_max_backlog=1200 net.ipv4.tcp_timestamps=0 net.ipv4.tcp_sack=0 net.ipv4.tcp_window_scaling=0 net.ipv4.tcp_max_tw_buckets=2000000 net.ipv4.tcp_mem=100000000 100000000 100000000 net.ipv4.tcp_wmem=100000000 100000000 100000000 net.ipv4.tcp_rmem=30000000 30000000 30000000 net.ipv4.ip_conntrack_max = 231072
- 23. Keepalive - On or Off? • reduces overhead of establishing new connections for each request from the browser • can waste memory and other resources if left open too long • Common practice is to disable them • I turn keepalive on, set to 6 seconds or 500 requests • For CDNs like Akamai, you’ll want to turn up the time to more like 120 seconds
- 24. GZip - mod_deflate • gzip compressing text resources - html, js, xml, css dramatically decreases the size of the response for those assets: often up to 90% reduction in size • reduces transfer time, especially for clients with slower connections (or big files) • This decreases page load time (Client) and reduces the time the server thread is sending the response (Server) # Removing Hosts vary Header unset Vary <IfModule mod_deflate.c> AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css application/x-javascript BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4.0[678] no-gzip BrowserMatch bMSIE !no-gzip !gzip-only-text/html </IfModule>
- 25. Browser Caching • Tell the browser to cache all static assets, for as long as you can bear it • Set the ETag • Set cache control and expiration response headers <LocationMatch '^/pca/images/.*'> FileETag MTime Size Header set Cache-Control "max-age=2764800, public" <IfModule mod_expires.c> ExpiresActive On ExpiresByType image/jpg A2764800 ExpiresByType image/jpeg A2764800 ExpiresByType image/png A2764800 </IfModule> </LocationMatch>
- 26. Disk Caching • Why not use mod_mem_cache? • Transparent web server caching of assets reduces load without deployment and development complexities • Some warnings! • Doesn’t auto clean itself • Can grow to be huge if you don’t check the headers being cached • Can grow to be huge if you have dynamic URI content - blah.jpg;jsessionid=foo • Another place to purge cache for changed files
- 27. Disk Caching - Config <IfModule mod_disk_cache.c> CacheRoot /var/cache/mod_disk_cache CacheDirLevels 2 CacheDirLength 1 CacheEnable disk /pca/img CacheEnable disk /pca/flash CacheEnable disk /pca/css CacheEnable disk /pca/js CacheEnable disk /pca/images CacheMaxFileSize 200715200 CacheDefaultExpire 3600 CacheIgnoreHeaders Set-Cookie </IfModule>
- 28. Mod_PageSpeed • Open Source Apache Module • Lots and Lots of filters • image compression • combine js/css • sprite images • domain sharding • etc...
- 29. Three Tier Architectur e • SSL Termination • Load Balancing • Mod_proxy/mod_cluster • Mod_Security
- 30. Building Scalable Clusters w/Apache • VIP • heartbeat • haproxy • DNS LB • simple round robin • smart
- 31. Questions?
Notes de l'éditeur
- Been doing this for 14 years. 10MinuteMail handled a Slashdotting, front page listing on Yahoo Tech, and front page Digg at the same time. Worked on sites such as AT&T.com, People’s Choice Awards, Payless Shoes, Vermont Country Store.
- When a user sees the page start loading, to when they can do stuff, to when the browser’s loading animation is done. Use Ajax to pre-populate fields, type-ahead, real-time field validation, reduce the number of full page submits/requests. Solving for client side performance can have a dramatic impact on the server side performance. Cached assets draw pages faster AND reduce requests the server has to handle.
- In engine building they say “Build for torque and the horsepower will follow”
- We’ve all seen these stats, but they’re worth repeating. This isn’t ivory tower stuff, this is simple business.
- Why not nginx (engine-X), Lighttpd, etc...? Extensions like mod_pagespeed, mod_cluster, and more.
- The problem with Apache configs are that the defaults are typically extremely out of date and based on much older hardware, network bandwidth, browser abilities, and application complexity
- Limited testing I did with Event MPM shows it’s ~5% faster than Worker, without real tuning.
- Just set it and forget it. If you have memory leak issues, set MaxRequestsPerChild to something like 5,000.
- This last setting (or larger) will keep your kernel from dropping incoming connections under high load
- Defaults are On, 15 seconds (too long), 100 requests (too small)
- This is HUGE! You can reduce the number of HTTP requests you have to handle by an order of magnitude or two by setting good cache headers.
- Mod_mem_cache has some bad bugs. mod_disk_cache lets the kernel’s in memory file caching algorithm do all the heavy lifting without tuning or exhausting available memory. For 3 tier environments, it’s common to have static assets that get deployed to the web servers separately from the application itself. This makes deployments more complex and error prone and makes local dev environments much harder to keep up to date. Seam and richfaces image tags insert jsessionid to URI, etc...
- I know a previous presentation was done on mod_pagespeed, so I won’t dive too deeply into all of it’s features and configs. Trying to optimize for performance can make dev more complicated. packtag. pagespeed.
- Apache is key for 3-tier architectures. It provides significant performance, security, and PCI compliance wins. Big improvements in Mod_proxy_balancer with 2.4 (dynamic cluster, session bleedoff, etc)