MarkMagnus
Distillery staging release does not bundling :fprof
Want to run fprof through a rpc
def profiler() do
:fprof.trace([:start, verbose: true, procs: :all])
spawn fn ->
:timer.sleep(60_000)
:fprof.trace(:stop)
:fprof.profile()
:fprof.analyse(totals: false, dest: 'textbook.analysis')
end
end
I thought by adding “set include_system_libs: true” to rel/config.exs would include the :fprof
But what I get is
PC to 'textbook@127.0.0.1' failed: {'EXIT',
{undef,
[{fprof,trace,
[[start,{verbose,true},{procs,all}]],
[]},
{'Elixir.Release.Tasks',profiler,0,
[{file,
"lib/textbook/release_tasks.ex"},
{line,31}]},
{rpc,'-handle_call_call/6-fun-0-',5,
[{file,"rpc.erl"},{line,197}]}]}}
So sad
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 4 of 4 Posts
NobbZ
include_system_libsdoes include the ERTS AFAIK, so you do not need to install erlang at the host.To actually get the
:fprofapplication into your release, you have to add it under your (extra_)applications-key inmix.exs.vfsoraki
When I add
:fproftoextra_application, my application does not start with error:I also can not use
:fprofin my production system for profiling. But I am able to use:fprofin development, without adding:fproftoextrac_applications.Elixir/Erlang version:
NobbZ
:fprofis part of erlangs:toolsapp, perhaps it helps to add that one.In general, when you have installed erlang globally then you have this app usually available, but for a bundled release, it is a bit different. A bundled release can only see dependencies which are bundled. It will never use globally installed modules or applications (well, when not bundling ERTS then
:stdliband:kernelare used from the installed ERTS, but thats it). This is to ensure reproducability.So, either find the correct application to bundle, or even better, do not profile on production. It will slow down your system drastically, dramatically increase its memory consumption and probably crash your BEAM.
vfsoraki
I’m aware of performance degration when profiling, but I need it to be on production, under load, to see what is causing high cpu usage.
The
:toolsapp did work, thanks!