Ruby Proxies for Scale, Performance, and Monitoring - GoGaRuCo - igvita.com
36 likes8,980 views
The document discusses the use of Ruby proxies for enhancing scalability, performance, and monitoring in event-driven architectures. It highlights various challenges in staging environments and proposes a duplex Ruby proxy solution for simulating real production traffic and optimizing performance. Additionally, it presents a case study involving the integration of a proxy with beanstalkd and a custom scheduler to improve resource efficiency and reduce costs.
![%w[ <Transparent> Intercepting Caching … ] solution for every problem](https://image.slidesharecdn.com/igvita-gogaruco-proxies-090417152908-phpapp01/85/Ruby-Proxies-for-Scale-Performance-and-Monitoring-GoGaRuCo-igvita-com-28-320.jpg)
![%w[ Transparent <Intercepting> Auth Cache … ] easy to make & a powerful hammer](https://image.slidesharecdn.com/igvita-gogaruco-proxies-090417152908-phpapp01/85/Ruby-Proxies-for-Scale-Performance-and-Monitoring-GoGaRuCo-igvita-com-40-320.jpg)
Ruby Proxies for Scale, Performance, and Monitoring - GoGaRuCo - igvita.com
- 1. Ruby Proxies for Scale, Performance and Monitoring Ilya Grigorik CTO / AideRSS Event-Driven Architectures @igrigorik #meshu #eda http://bit.ly/eda
- 2. postrank.com/topic/ruby The slides… Twitter My blog
- 3. Proxy Love
- 4. Myth: Slow Frameworks “ Rails, Django, Seaside, Scala…” cant scale.
- 6. The “More” Proxy Solution
- 7. Transparent, Cut-Through Proxy Transparent
- 8. Transparent Proxy = Scalability Power Tool 90% use case
- 9. Proxies for Monitoring, Performance and Scale welcome to the wonderful world of intercepting, caching, … , proxy servers
- 10. Problem: Staging Environment Production Simulated User
- 11. “ Representative Load / Staging” Duplication Simulating traffic?
- 12. Staging fail. Profile of queries has changed Fail Load on production has changed Fail Parallel environment Fail Slower release cycle Fail
- 13. Replay log data, rinse, repeat github.com/igrigorik/autoperf
- 14. Benchmarking Proxy flash of the obvious Real (production) traffic Duplex Ruby Proxy, FTW!
- 15. Transparent Duplex Proxy, FTW
- 16. Same response, different turnaround time Different response body!
- 17. github.com/igrigorik/em-proxy Duplex Ruby Proxy, FTW!
- 18. EM-Proxy Workflow 1. Accept connection - Connect & Forward to Production - Connect & Forward to Staging 2. Stream response to client from Production - Buffer response from Staging 3. Run “Processor / Analyzer” once both return
- 19. Ruby EventMachine crash course EM::Connection #receive_data - new data ready for processing #unbind - connection terminated #connection_completed - connected
- 21. Forward Production Response Analyze Results
- 22. Open connection to application server
- 24. Pass response to Duplex Notify when done
- 26. Analyze Time, Response… Response Time
- 27. Cute, right? but so what…
- 28. %w[ <Transparent> Intercepting Caching … ] solution for every problem
- 29. Validating Proxy easy, real-time diagnostics Woops!
- 30. Who said you’re not allowed to touch the data? Intercepting Proxy for those hard-to-reach spots
- 31. SMTP / Mail: inject SPAM detection De(encrypt): stream data MySQL: inject sharding logic Intercepting Proxy for those hard-to-reach spots
- 32. @PostRank: Beanstalkd + Ruby Proxy because RAM is still expensive
- 33. Beanstalkd Math ~ 93 Bytes of overhead per job ~300 Bytes of data / job x 80,000,000 jobs in memory ~ 30 GB of RAM = 2 X-Large EC2 instances Oi, expensive!
- 34. Extending Beanstalkd Observations: 1. Each job is rescheduled several times 2. > 95% are scheduled for > 3 hours into the future 3. Beanstalkd does not have overflow page-to-disk Memory is wasted… We’ll add it ourselves!
- 35. @PostRank: “Chronos Scheduler” 1 “Medium” EC2 Instance Intercepting Proxy
- 36. Extend the protocol Chronos Scheduler Beanstalkd persistence Process incoming data Buffer “SCHEDULE” requests, otherwise forward
- 37. Archive to MySQL Chronos Scheduler Beanstalkd persistence Buffer “SCHEDULE”
- 38. @PostRank: “Chronos Scheduler” Extend the protocol ARCHIVE RESERVE, … 10 line patch to client: queue.archive(job)
- 39. @PostRank: “Chronos Scheduler” ~79,000,000 jobs, 4GB RAM ARCHIVE RESERVE, … Upcoming jobs: ~ 1M 400% cheaper + extensible! 1 Proxy, 1 Beanstalkd, 1 MySQL = 200 req/s
- 40. %w[ Transparent <Intercepting> Auth Cache … ] easy to make & a powerful hammer
- 41. Cheers. Questions? The slides… Twitter My blog
Editor's Notes
- #2: Wonderful, wonderful world in the context of building and using Ruby proxy servers for scale, performance and monitoring.