Successfully reported this slideshow.
Your SlideShare is downloading. ×

How to Build a High Performance Application with PHP and Swoole?

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 48 Ad
Advertisement

More Related Content

Recently uploaded (20)

Advertisement

How to Build a High Performance Application with PHP and Swoole?

  1. 1. @JomLaunch 2021 Build your High Concurrency App with PHP and Swoole Albert Chen
  2. 2. About Me { "data": { "human": { "name": "Albert Chen", "occupation": "Software Architect", "website": "https://albert-chen.com", "interests": [ "traveling", "programming", "cooking" ] }, "tags": [ "Laravel Artisan", "Swoole Enthusiast", "Open Source Contributor" ] } }
  3. 3. Outline • Introduction of Swoole • PHP’s Internal Lifecycle • Blocking I/O in PHP • Server Structure of Swoole • Benchmark of Swoole • Coroutine in Swoole • Some Facts about Swoole • Q&A
  4. 4. Slido Join at slido.com #760920
  5. 5. Slido Join at slido.com #760920
  6. 6. What is Swoole?
  7. 7. What is Swoole? • Since 2012 • Open source based on Apache-2.0 License • 17k stars until July 2021 • More than 100 contributors • Adopted by many enterprises in China • O ffi cially supported by Laravel Octane
  8. 8. What is Swoole? • A C extension for PHP • An asynchronous network engine for PHP • Features: • Event-driven non-blocking I/O • HTTP / HTTP2 / Websocket / TCP / UDP • Coroutine (CSP Model) • Excellent performance for high concurrency
  9. 9. What is Swoole? • Not a new language, but an extension for PHP • Provides many new features for traditional PHP • New lifecycle in Swoole • Server patterns, coroutine, async I/O, Process Management, etc. • It's still under active development • Stable for production environment • High performance
  10. 10. Usage Statistics for Websites
  11. 11. PHP’s Benchmark https://kinsta.com/blog/php-benchmarks/
  12. 12. Benchmark Comparison https://www.toptal.com/back-end/server-side-io-performance-node-php-java-go
  13. 13. Why PHP Performs Poorly in High Concurrency?
  14. 14. PHP Lifecycle
  15. 15. How many files are required for one request in Laravel? 426 get_included_files() In Laravel 8.52
  16. 16. Stateless PHP • How do we serve PHP today? • PHP-FPM • mod_php for Apache • Both patterns are all stateless
  17. 17. Stateless PHP • Pros • Easy scaling • Simple, less risk causing memory leaks • Cons • States can't be shared between requests • States must rely on external storages • Resources can't be reused e ffi ciently • Connection cost is expensive (like database) • Not good for high performance
  18. 18. Blocking I/O in PHP • PHP is originally created as glue layer to call C functions • The I/O model is blocking by default • Almost all client-side libraries involving I/O are blocking • Multiple process for handling blocking I/O • I/O bound concurrency depends on process number • Cost for context switch in processes is expensive
  19. 19. Blocking I/O in PHP • Resource can't be reused • I/O requests are blocking • 80% time cost on blocking I/O
  20. 20. Blocking I/O in PHP
  21. 21. Event Loop in NodeJS
  22. 22. Concurrency Problem • 100 requests at the same time need 100 processes • 100 connections will be established as well • Scale to increase concurrency
  23. 23. Let’s See What Changes in Swoole
  24. 24. Server Structure in Swoole
  25. 25. PHP Lifecycle in Swoole Run only once!
  26. 26. Server Structure in Swoole • Code Is Persistent in Memory • Swoole Server Takes Lifecycle Over PHP • Reduce Initialization Steps • Reduce Response Latency • Event-driven Non-blocking I/O for Requests
  27. 27. Benchmark Comparison between Go and Swoole
  28. 28. Server Benchmark in Go
  29. 29. Server Benchmark in Go
  30. 30. Server Benchmark in PHP
  31. 31. Server Benchmark in PHP
  32. 32. This Doesn’t Mean PHP with Swoole is Faster Than Go (Of Course Not)
  33. 33. Coroutine in Swoole
  34. 34. Coroutine in Swoole • Non-Blocking I/Os are scheduled by coroutine automatically. PHP is the best Swoole is awesome! Hello world!
  35. 35. Coroutine in Swoole Hello Swoole 1.2.3.4 • Non-Blocking I/Os are scheduled by coroutine automatically.
  36. 36. Coroutine in Swoole 1.2.3.4 1.2.3.4 1.2.3.4 1.2.3.4 … Hello Swoole! • Non-Blocking I/Os are scheduled by coroutine automatically.
  37. 37. Coroutine in Swoole Hello Swoole! 1.2.3.4 1.2.3.4 1.2.3.4 1.2.3.4 … • Non-Blocking I/Os are scheduled by coroutine automatically.
  38. 38. Coroutine in Swoole • CSP Model 1 2 3 4 5
  39. 39. Some Facts about Swoole • Most of traditional PHP projects needs to be refactored. • Convert requests and responses
  40. 40. Some Facts about Swoole • Global states in PHP needs to be used more carefully. (eg. $_GET, $_POST, static, global)
  41. 41. Some Facts about Swoole • Global states in PHP needs to be used more carefully. (eg. $_GET, $_POST, static, global)
  42. 42. Some Facts about Swoole • Don’t use exit/die function in your PHP application.
  43. 43. Some Facts about Swoole • Memory leak may happen!!!
  44. 44. Some Facts about Swoole • You can try Hyperf framework for your new projects. Hyperf = Hyperspeed + Flexibility https://www.hyperf.io
  45. 45. Some Facts about Swoole • Swoole is now o ffi cially supported by Laravel team. • Laravel will become friendly in long-running server • Some Octane features rely on Swoole • No coroutine features are supported yet
  46. 46. Some Facts about Swoole • There’s knowledge gap for traditional PHP developers.
  47. 47. Q&A

×