josefrichter
Understanding appsignal output and digging deeper to identify bottlenecks
Hi, I was playing with AppSignal today and this is example output of measuring a post request into one of my api endpoints, which I generally expect to be the slowest one – exclusive table lock to perform a count operation and then conditional insert, with potentially tons of parallel requests coming in.
^ from this chart, I don’t really understand what is really happening between 0-200ms. Also the very first query.ecto there is actually CREATE TABLE IF NOT EXISTS "schema_migrations"... – I don’t know what that really is and why is it happening on api post request? So I understand what’s going on from call.phoenix_endpoint onwards, but before that?
Can you please advise? Thank you
Most Liked
benwilson512
A big thing with localhost is the code reloader. Any request is gonna hit the phoenix code reloader which is gonna check to see if any code needs to be recompiled. Also keep in mind that mix lazy loads code so the first request or two will have extra latency from needing to load code.
At a minimum turn off code reloading.
josefrichter
thanks a lot! I dug deeper into this topic and basically deployed a production app on localhost. the numbers are significantly different now ![]()
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










