sahilpaudel
While checking my API metrics in new relic and found queries are getting executed with response time in a few ms, but there is a field for #PID<0.30881.849> which took 300ms+ to process.
Below is the table
| Category | Slowest components | Count | Duration | % |
|---|---|---|---|---|
| pid<0.30881.849> | pid<0.30881.849> | 1 | 379 ms | 97% |
| Database | Postgres rules_engine_test_cases select | 1 | 2 ms | 1% |
| Database | Postgres rules_engine_conditions select | 1 | 1 ms | 0% |
| Database | Postgres rules_engine_results select | 1 | 1 ms | 0% |
| Database | Postgres rules_engine_new_audit_logs insert | 1 | 1 ms | 0% |
| WebTransaction | /Diamond.Web.RuleSetController/select_evaluate | 1 | 0 ms | 0% |
| Remainder | Remainder | 1 | 7 ms | 2% |
| Total time | 391 ms | 100% |
Can you please help me understand this as it is causing few timeouts as well?
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
- #deployment
- #library
- #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
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #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.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
Without knowledge of what is that PID doing and how it is implemented, then it is quite hard to tell.
sahilpaudel
It is an old code and I got to work on it.
PID is the process id that is processing the current request I guess.
sahilpaudel
It will just show that the PID is taking 300ms
sahilpaudel
All I can find in the new relic is Application code (in pid<0.21415.227>) is taking 99% of the total processing time which is 5690ms which is huge.
Can you please help me understand from the new relic perspective @binaryseed
wanton7
Reason why you are not getting almost any answers is that what you are asking is basically someone else to do your work for you. Also they can’t give you any answers because they don’t have access to your code and if they did they would have to what you need to do and that is to find out what part of your code is slow. If someone asked something like that from you would you be able to answer?
I don’t work with Elixir professionally but first thing I would do is to find out what parameters where given to the request. Then try to get same problem appear in your local environment and start profiling. I haven’t yet used any Elixir/BEAM profiling tools because I haven’t had any performance problems with my small projects. With small bit of googling I found this blog how to do performance profiling in Elixir https://medium.com/@victor.nascimento/an-elixir-performance-tooling-story-c5c85479063a
Sebb
Here is an example how you could tackle this: