ketupia
I’m a solo indie developer and built a Phoenix LiveView app. It’s an interactive multiplayer experience and I don’t know how to know how well it performs with varied devices, varied connectivity, and under load.
I’ve posted ti r/TestMyApp and that may prove to be fabulous but I’m thinking that will be individuals testing at their own pace.
What other ways can I test multiplayer loads and iteractivity?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
The way we do this on most projects that solve business problems is to send metrics from the parts of system you care about. What is even nicer is that a lot of libraries emit them by default, all you have to do is hook to them, for example phoenix: Telemetry — Phoenix v1.8.8
In that way, you can later query them and analyze your overall performance of the system and find the bottlenecks.
There is also the option of spinning up another instance that is as close as possible to what you have in prod and create a custom stress testing client. I highly doubt there is any libraries for doing this, so it’s up to you to build this from scratch. This approach has its own benefits, however the effort investment in making this work correctly is times bigger than the above approach.
Also Liked
namxam
I think using telemetry is the way to go. Although it might be a very good idea to have manual tests as well. I guess you will have a max number of simultaneous users.
I would deploy it on a production server and get some friends, a crate of beer and start testing.
When those tests work as expected, I would continue with a closed beta test with a limited number of players.
And then slowly add more players via additional slots.
And while you do this, always track your telemetry data.