-
Notifications
You must be signed in to change notification settings - Fork 662
How do I scale this laravel-websockets package? #1045
-
I am currently building a website that uses Live chats. Its currently working now as expected.
I am running the php artisan websocket:serve via supervisor.
My worry now is what will happen if there are thousands of concurrent users using my website.
And I have these 2 questions:
- How do I monitor if hitting the server limit?
- If there are more concurrent users does it mean it needs uses more memory? So if I'm expecting a lot of users visiting the website do I need to increase
memory_limitinphp.ini? Do I need to tweak any more settings?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment
-
The current solution is pretty scalable and can handle a large number of connections. Not sure if you've already seen this section of the docs but it can handle close to 60,000 concurrent connections with just a couple GB.
Unless you're running a really high traffic site (keeping in mind that a daily traffic flow of 1 million users averages out at 695 users a minute) I wouldn't worry too much.
Having said that, I believe version 2 will be shipped with replication allowing events to be broadcast across multiple instances, introducing redundancy and allowing distribution of subscriptions across multiple servers. I'm looking forward to this as it will allow me to introduce redundancy and scalability on my Kubernetes cluster for example.
Beta Was this translation helpful? Give feedback.