Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (11)
Similar a Building & Testing Scalable Rails Applications
Similar a Building & Testing Scalable Rails Applications (20)
Último
Último (20)
Building & Testing Scalable Rails Applications
- 1. Building & Testing Scalable Rails Applications
- 2. Mike Smith • Technical Lead - Blitz.io • Ruby developer • @evilmike
- 3. Building a scalable app
- 4. A typical Rails stack Nginx+Passenger • Passenger forwards HTTP requests • Rails processes generate responses • Database is shared by all Rails processes
- 5. Rails concurrency • Multiple Rails worker processes per server • # of processes is limited by available memory • Each Rails process handles one request at a time
- 6. Key Concept! • There’s a finite number of requests that can be handled concurrently • Additional requests wait until the next Rails process becomes available
- 7. Speed up your slow requests
- 8. Database Queries • Identify slow database queries • Optimize queries & add table indexes • ActiveRecord::Base.explain (Rails 3.2)
- 9. Rails Caching • Page Caching • Action Caching • Fragment Caching • Low-level Caching
- 10. Long-running Tasks • Don’t execute long-running tasks in the request handler • Use background workers Resque, Delayed Job
- 11. Free Rails to handle dynamic requests
- 12. Static Content • Serve with Nginx, Apache, etc. • CSS, Images & Javascript • User-uploaded & generated files (S3, etc) • Consider using a CDN
- 13. HTTP Caching • Caching layer in front of your Rails process • Varnish & Rack::Cache • Expiration model • Expires: Fri, 28 Sep 2012 01:12:32 GMT • Validation model (Conditional GET) • Last-Modified: Wed, 29 Aug 2012 04:58:08 GMT • ETag: ae7d971f0
- 15. Scale vertically
- 16. Increase the size of your servers • More memory, More CPU • Good for Database servers & Caching servers
- 18. Add more servers • Serve more requests at a time • Good for Application servers & Background workers
- 19. Two app servers HTTP Load Balancer Nginx+Passenger Nginx+Passenger
- 21. 2 Application Server Instances 4 Application Server Instances
- 23. Test in a realistic environment • Use realistic data • Use an environment that replicates production
- 24. Consider your location • Latency can affect load test results • Consider running your load test from the region where most of your users originate
- 25. Consider the effects of caching • To test worst-case performance, you may need to bust some caches • Vary the URL or query parameters GET /blog/article_1 GET /blog/article_2 GET /blog/article_3 ...
- 26. Pay attention to request headers • Emulate the HTTP headers of your expected clients • Accept-Encoding: gzip, deflate • Accept: */* • User-Agent:
- 27. Try • Sign up & test with 250 virtual users for free • Engine Yard Cloud users • http://cloud.engineyard.com/addons/blitz • Or signup directly • http://blitz.io