Serverless, ReactPHP, and Expanding Frontiers, May 2019

4 \ May 2019 \ http://www.phparch.com

Deploying ReactPHP Applications

classes, and generally attempts to crash
explosively.
The solution to this is to raise the
hard and soft limit for your applica-
tion’s user. Before you do that, you have
to determine what to raise it to. Your
peak user count plus 15% as the margin
is a good bet. However, that doesn’t take
into account when your site goes viral.
ReactPHP is single threaded at its core,
so at some point, you’ll saturate a CPU
core. You can spawn multiple processes,
and even listen on the same IP:port with
react/socket’s^8 so_reuseport option for
TcpServer^9 to spread the load. You still
have to come to a limit matching the
resources available on your infrastruc-
ture, your architecture, and the usage of
your application. Setting the limits to
150.000 should get you started but it, as
always needs, monitoring.

php.ini
By default PHP lets you use 128MB
of memory. This might be more than
enough for your app, or not at all. As
with ulimit do some research on how
many users you expect and how much
memory your application needs. PHP’s
memory comes in two flavors, the
internal usage (the memory your appli-
cation uses) and the allocated memory
by the PHP process. The latter will
always be higher because it allocates
pages of memory for the application
running inside PHP to use. As a rule
of thumb, leave at the very least 50% of
the available free for the OS and other
services you run aside your application.
My memory limit is set to 1GB, and
increasing that when it starts to run out.
(But only when a memory leak in the
application doesn’t cause it.)

8 react/socket’s :
https://reactphp.org/socket/
9 TcpServer:
https://reactphp.org/socket/#tcpserver

When developing an application

with react/http be sure to tweak the

post_max_size INI setting as well.

Together with memory_limit it is used

to configure React\Http\Server where a

POST message cannot cause you to run

out of memory. It does so using the

following calculation: (memory_limit

/ 4) / post_max_size. The middleware

automatically set up in React\Http\

Server also respect max_input_vars, and

max_input_nesting_level to prevent

Figure 1. Memory Graph

Listing 1

1. version: 2


2. jobs:


3. build:


4. docker:


5. 
   
   
   
   • image: wyrihaximusnet/php:7.3-nts-alpine3.9-dev
   
   
   
   


6. 
   
   
   
   • image: rabbitmq:3.5.
   
   
   
   


7. working_directory: ~/repo


8. steps:


9. 
   
   
   
   • checkout
   
   
   
   


10. 
    
    
    
    • run: cp .env.example .env
    
    
    
    


11. 
    
    
    
    • run: composer install -n --ansi --no-progress --optimize-autoloader
    
    
    
    


12. 
    
    
    
    • run: ls -lasth
    
    
    
    


13. 
    
    
    
    • run: make
    
    
    
    


14. 
    
    
    
    • run: rm .env
    
    
    
    


15. 
    
    
    
    • run: composer install -n --ansi --no-progress --optimize-autoloader --no-dev
    
    
    
    


16. 
    
    
    
    • run: echo $CIRCLE_TAG >> ~/repo/version
    
    
    
    


17. 
    
    
    
    • persist_to_workspace:
    
    
    
    


18. root: ~/repo


19. paths:


20. 
    
    
    
    • ./*
    
    
    
    


21. deploy:


22. docker:


23. 
    
    
    
    • image: ansible/ansible:ubuntu
    
    
    
    


24. environment:


25. ANSIBLE_HOST_KEY_CHECKING: no


26. working_directory: ~/repo


27. steps:


28. 
    
    
    
    • checkout
    
    
    
    


29. 
    
    
    
    • attach_workspace:
    
    
    
    


30. at: ~/repo


31. 
    
    
    
    • run:
    
    
    
    


32. name: Install System Packages


33. command: pip install ansible


34. 
    
    
    
    • run: ansible-galaxy install -r .circleci/requirements.yml
    
    
    
    


35. 
    
    
    
    • run: ANSIBLE_FORCE_COLOR=true ansible-playbook -i .circleci/hosts.ini
      .circleci/deploy.yml
    
    
    
    


36. workflows:


37. version: 2


38. build-n-deploy:


39. jobs:


40. 
    
    
    
    • build:
    
    
    
    


41. filters:


42. tags:


43. only: /.*/


44. 
    
    
    
    • deploy:
    
    
    
    


45. requires:


46. 
    
    
    
    • build
    
    
    
    


47. filters:


48. tags:


49. only: /.*/


50. branches:


51. ignore: /.*/