Thanks for asking, I am planing to add docuemention to explain it.
Comparison to Greys
Pros
Arthas is derived from Greys, we thank very much for the previous work done by Greys. In Alibaba we made several enhancement:
- Better user experience, e.g. auto complete, command history, auto suggestion, it works more like a real terminal.
- Support both telnet and websocket, they both share the same experience. You can diagnostic both on the command line and on the browser.
- More functionality: e.g. JAD, dashboard, thread, classloader.
- Improved stability: It has been widely used inside Alibaba's production system for 2~3 years, and it is proven to be stable. We've fixed couple of issues found with Greys. Some of them are fixed also by greys (e.g. memory leak when using groovy scripts, we use ognl to replace groovy scripts), some of them are not (e.g. classloader leak issue). And we have done a lot of work to protect Arthas from harming your JVM (e.g. limit the size of output, ensure the resource are gracefully released after Arthas shutdown, performance optimization and etc.)
Cons
- Arthas does not support customized commands, while Greys support customized written in JavaScript.
- Greys have a powerful command call ptrace, which is the combination of trace and tt, while Arthas does not.
Comparison to JVM-sandbox
TODO
Most helpful comment
Thanks for asking, I am planing to add docuemention to explain it.
Comparison to Greys
Pros
Arthas is derived from Greys, we thank very much for the previous work done by Greys. In Alibaba we made several enhancement:
Cons
Comparison to JVM-sandbox
TODO