High Concurrency Architecture and Laravel Performance Tuning
10 likes20,786 views
This document summarizes techniques for improving performance and concurrency in Laravel applications. It discusses caching routes and configuration files, using caching beyond just the database, implementing asynchronous event handling with message queues, separating database reads and writes, enabling OPcache and preloading in PHP 7.4, and analyzing use cases like a news site, ticketing system, and chat service. The document provides benchmarks showing performance improvements from these techniques.
High Concurrency Architecture and Laravel Performance Tuning
- 1. High Concurrency Web Architecture and Laravel Performance Tuning @LaravelConf Taiwan 2019 By Albert Chen
- 2. About Me • Albert Chen • Software Engineer • M17 HandsUp • Open Source Maintainer
- 3. What Is High Concurrency?
- 4. What Is High Concurrency? PV = 2,000,000 (200w) QPS = (200w x 0.8) / (24 x 3600 x 0.2) 93 QPS 😀
- 5. What Is High Concurrency? 2,000,000 (200w) in 1 minute QPS = 200w / 60 33333 QPS 😭
- 6. What Is High Concurrency? Read in High Concurrency • Vertical Scaling • Horizontal Scaling • Content Delivery Network • Data Caching • Single Point Optimization Write in High Concurrency • Message Queue • Rate Limit • Maximum Serving Limit • Wait in Line • Rules Optimization
- 8. Performance Tuning in Laravel • Route and Config Files Cache • Cache (Not Limited to Database) • Async Event (Delayed Processing) • Database Read/Write Separation • OPCache • Preloading in PHP 7.4
- 9. Route and Config Files Cache php artisan route:cache
- 10. Route and Config Files Cache Register Route Route Register Route Route Register Route Route Route Collection • Lifecycle for Registering Routes
- 11. Route and Config Files Cache Unserialize Cached Serialized Route Collection Route Collection • Lifecycle for Routes Caching
- 12. Route and Config Files Cache Route Numbers No cache (ms) Cache (ms) Speed-up 1 2.5 1.9 1.3x 10 5.2 2.6 2.0x 100 22.5 4.3 5.3x 1,000 166 32 5.1x 10,000 1,513 334 4.5x https://voltagead.com/laravel-route-caching-for-improved-performance/
- 13. Route and Config Files Cache https://voltagead.com/laravel-route-caching-for-improved-performance/
- 14. Route and Config Files Cache php artisan config:cache
- 15. Route and Config Files Cache Merged Config File • Lifecycle for Config Caching Config Files
- 16. Benchmark Comparison • Provider: Google Cloud Platform • Instance Type: n1-standard-8 • CPUs: 8 vCPU Cores (Skylake) • Memory: 30 G • Disk: 20 G SSD • OS: Ubuntu 18.04 LTS • PHP Version: 7.3
- 17. Benchmark Comparison • Benchmark without Cache
- 18. Benchmark Comparison • Benchmark with Routes and Config Cache
- 19. Cache (Not Limited to Database) • Discover Hotspot Data (Hit Rate) • Proper TTL for Cached Data • Avoid Expiring Cache at The Same Time • Revoke Cache when Data Changes • Avoid Cache Missing • Hierarchical Cache Design • High Available Cache System • Warm Up the Cache
- 20. Cache (Not Limited to Database) • Revoke Cache when Data Changes
- 21. Cache (Not Limited to Database) • Avoid Cache Missing
- 22. Cache (Not Limited to Database) • Avoid Cache Missing Client Database Cache Layer Client Client
- 23. Cache (Not Limited to Database) • Hierarchical Cache Design Database Local Memory Local Memory Local Memory Cache Layer Cache Revoke
- 24. Cache (Not Limited to Database) • High Available Cache System https://rancher.com/blog/2019/deploying-redis-cluster/
- 25. Cache (Not Limited to Database) • Warm Up the Cache Request Request Request Request Cache Layer Database Time Consuming Query(Warm Up)
- 26. Async Event (Delayed Processing) Producer Kafka Rabbit MQ Queue Driver Consumer Producer Producer Producer Consumer Consumer Consumer (Laravel Event) (Laravel Queue Worker)
- 27. Database Read/Write Separation 20% on Write 80% on Read Master Slave Slave Slave Read Replicas
- 29. Database Read/Write Separation App Master Slave Slave Slave Read Replicas Write Read
- 32. Database Read/Write Separation Master Slave Slave Slave Read Replicas SQL Proxy Slave Write Read Read Read Read
- 34. OPCache PHP Files Tokenizing Semantic Parsing AST Generate Bytecode Execute Bytecode Output • Lifecycle in PHP with OPCache Load Bytecode From Memory Check Bytecode Cache
- 35. Benchmark Comparison • Benchmark with OPCache
- 36. Benchmark Comparison • Benchmark without OPCache
- 37. Preloading in PHP 7.4
- 38. Preloading in PHP 7.4 PHP Files Tokenizing Semantic Parsing AST Generate Bytecode Execute Bytecode Output Load Bytecode From Memory Check Bytecode Cache Preload in Memory • Lifecycle in PHP with Preloading
- 39. Preloading in PHP 7.4 composer require ayesh/composer-preload
- 40. Benchmark Comparison • Benchmark with Preloading Benchmark Preloaded files Server startup time Opcache memory used Per request memory used QPS No preloading 0 0.06 s 16 MB after warmup 1,825 KB 596 rq/s Preload hot classes 878 0.26 s 21 MB 869 KB 695 rq/s Preload everything 14541 1.56 s 105 MB 881 KB 675 rq/s https://github.com/composer/composer/issues/7777
- 42. Banana News • PV is around 200w • Large amount of content resource • Fuzzy search support • Changeable news rank by topics • 99% read, 1% write
- 45. Banana News Images Server (CDN) Load Balancer Master Slave Slave Slave Read Server Server Server
- 46. Banana News Images Server (CDN) Load Balancer Master Slave Slave Slave Read Redis Cache Server Server Server
- 47. Banana News Images Server Load Balancer Master Slave Slave Slave Read Redis Cache CDN Elastic Search Server Server Server eg. Cloudflare
- 48. AATIX • High concurrency in short period • Limited tickets for selling • High available service
- 49. AATIX Images Server Load Balancer Master Slave Slave Slave Read Redis Cache CDN Server Server Server
- 53. AATIX Master Slave Slave Slave Read Redis Cache Server Server Server Queue Local Cache Atomic Counter Rate Limit Circuit Breaking
- 54. AATIX • Avoid large amount of write requests at the same time • Queue • Rate Limit • Reduce repeated requests from clients • Service isolation for hotspot data • Circuit breaking for high availability
- 55. • Large amount of webhook calls • High availability for webhooks • Instant response time • Chat service for live streaming
- 56. HandsUp
- 57. HandsUp Facebook Webhooks Message Load Balancer Server Server Server Queue PubNub Service Analysis Service Swoole Service PubSub Many to Many Queue Workers
- 58. The Last But Not the Least
- 59. Q&A