-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impact of ErlangPL on the monitored system #32
Comments
To answer your question first: you should not run However we don't aim to be production monitoring system, because there is so much excellent and battle-tested software which does exactly that. We want to give BEAM developers a tool to quickly find potential bottlenecks and performance issues, when they are still developing their projects. We also believe in a value EPL has as a learning tool for newcomers. |
We should add it to README. |
Hello, so ErlangPL looks amazing, but I couldn't find any mentions of its impact on the monitored system. Erlang tools like
cprof
,eprof
andfprof
take a hit on the system and aren't recommended to be kept running in production.I guess ErlangPL uses the
:sys
module and:proc_lib
to retrieve runtime info from the system. Therefore, I'd like to know if ErlangPL is intended to be kept running as to monitor a running production system or if it's only meant for development and debugging.Thanks!
The text was updated successfully, but these errors were encountered: