To figure out if you have a CPU problem, I'd take a look at etop/dtop/entop and see if there are processes consuming a lot of reductions. If they're consuming these reductions in proportion to receiving a lot of input messages then they may be fine, but you can look at having multiple processes handle these messages in parallel. If they're just consuming lots of reductions, then check to see if the code in those processes can be made more efficient.
Björn-Egil, Erlang/OTP:
Eprof: Regarding the profiling guide, it states that *eprof* has
"significant slowdown", this is *untrue* and should be revised. *note to
self* It has some slowdown, (pulling some data from memory), I would say
2 - 6 times. Eprof also has very low impact on multiple schedulers.
Eprof does not produce a callgraph but it will tell you how much time
you spend in specific functions which is very helpful.
本文讨论了如何使用top/dtop/entop等工具来诊断CPU问题，特别是针对进程消耗大量资源的情况。同时介绍了eprof工具的实际性能影响及使用场景，指出其在多调度器环境下具有较低的影响，并能有效帮助开发者了解特定函数的运行时间。
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
