Tool for developers working with systems running on the Erlang VM (BEAM). It helps with performance analysis.
name column in the ETS node view (@mkacper)epl-ets UI plugin code style (@Baransu)The 0.9.0 release contains all the work done during Google Summer of Code program. The main feature introduced in this release is new ETS details view. The view visualises all the traffic between an observed ETS table and processes that communicates with it.
The release also introduces Quick start guide which explains step by step the whole process of running ErlangPL script. It can be helpful especially for the Erlang/Elixir newcomers. Apart from that there are some small internal changes in this release (see above).
The 0.8.0 release introduces two views. The ETS node view is a result of the 2nd Google Summer of Code project's milestone. It makes it possible to see all the ETS tables present on a particular node with their statistics. Statistics are some basic information about the table (name, memory, size) and some more sophisticated ones like insert/lookup max time or the number of calls to this functions.
Timeline view allows users to trace the selected Pid. The tracing means that the view shows the every message received by the process identified by the Pid and the process's state just after it handles the message.
make release rule (@Baransu)undefined supervisors' children PIDs (@arkgil)erlangpl-ui repository into erlangpl repository (@Baransu)epl_st plugin repository into erlangpl repository (@Baransu, @arkgil)erlangpl-ui version (@Baransu)We added new view, which renders traffic between the observed node and other connected nodes. Traffic received from the connected nodes is marked in yellow and the outgoing traffic is marked in blue. Example animations were posted on YouTube. More detailed release notes were posted on erlangpl-ui.
This release brings also experimental visualisation of message passing between processes.
Last month we published a poll on Twitter asking which web technology to use for our UI? We received 440 responses with 39% votes for React and 36% votes for Elm. Based on this feedback we decided to rebuild the UI from scratch in React and add an Elm-based component to demonstrate how the two technologies can co-exists. Our hope is that this approach will allow contributions from developers familiar with React, but also those who want to give Elm a try.
Over the last few weeks we also discussed whether the 3D view present in the 0.3.0 release is suitable for visualising supervision trees. The initial prototype indicated it may be hard to achieve a good UX with 3D visualisation, so we switched to a graph drawing library that uses WebGL, but renders 2D views.
Thank you to our contributors: @arkgil, @Baransu and @michalslaski