din_S
Phoenix performance issues with API
I’m using Phoenix to build a simple API that takes an HTTP request (JSON) and add the IP and user-agent to it and then insert it in MongoDB
def imp(conn, params) do
params=Map.put(params,"ip",conn.remote_ip |> Tuple.to_list |> Enum.join("."))
params=Map.put(params,"ua",get_req_header(conn, "user-agent"))
Mongo.insert_one(:mongo, "impression", params)
json(conn, %{})
end
and it worked well, but what really is surprising is the performance, I have implemented the same function using NodeJS and this was the responses time of both:
Node Phoenix
#1 237 ms 4s
#2 65 ms 571ms
#3 30 ms 575ms
#4 33 ms 581ms
#5 27 ms 577ms
#6 30 ms 571ms
#7 31 ms 567ms
I have read about phoenix performance and how it should respond in microseconds time.
I thought that dealing with MongoDB is the issue, so I delete the insertion code but I still get 953ms response time (the first time) and 89ms, 350ms, 69ms the other times
so why my phoenix app is not that fast?
Note: I’m using Windows and Postman
Marked As Solved
wanton7
code_reloader: true in dev.exs can cause this, try setting it to false. But you shouldn’t test response times in dev mode any way. Also I’m sure that almost no one uses Windows in production so it might not be up to par with with Unix/Linux. If you want to test response times in Windows I would use WSL (Windows Subsystem for Linux) and run your app there in prod mode.
Also Liked
sasajuric
Definitely test in prod like others already suggested. Also make sure that not too much logging occurs, e.g. by setting the log level to warn. There are a few other minor tips which can improve numbers. I blogged about it here. The article is 4 years old, but hopefully most of the tips still apply ![]()
din_S
Thank all of you guys.
Actually, your responses are relieving
I have tried to set code_reloader: false and I started to get 30 ms responses and I will benchmark the app in production mode next times
lucaong
Consider that we’re getting in the realm of micro-optimizations here. At the point when you add a call to MongoDB, especially if synchronous, it probably does not make sense to optimize Map.put vs. Map.merge and rather use whatever is more readable, as the database IO would dominate the time.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








