ETS
The ETS plugin allows users to analyse ETS performance from different perspectives. The plugin delivers 3 views which can be seen as layers through which you can look at the ETS tables. The idea is simple — if you want to trace a problem related to an ETS table, you start from the top-level view (the most general one) and go down through the subsequent layers (views) until you reach the one that will help you identify the source of the problem you are looking for. The scheme of the views looks as follows: cluster view (shows all the nodes in a cluster) -> node view (shows all ETS tables on a node) -> ETS details (shows more detailed information).
The ETS plugin with all the functionalities implemented was released in the erlangpl 0.9.0.
Keep in mind that the ETS node view and ETS details view relay on Erlang tracing. Because of that, erlangpl could go down if it connects to a system under heavy load.
- Run the erlangpl (follow these steps)
- Go to web UI http://localhost:37575
- Choose the ETS icon from the sidebar on the left
When you click on the ETS icon mentioned in the previous section you will see the ETS cluster view.
- number of the ETS tables present on a node
- allocated memory usage for the tables.
The view will appear when you click on a node (dosen't matter which one) in the ETS cluster view.
ETS node view shows a table in which every single row presents information about one ETS table from the clicked node. It is possible to choose which columns of the table are visible and sort columns which hold numerical values.
This view will appear when you double click on a particular row in the ETS node view table.
It takes some time to render a graph. The graph is very similar to the one in the Traffic view section. The view visualises an ETS table (the big circle) and the processes (the small circles) which are trying to write to or read from it. There is information on the table representation how many inserts/reads a particular table has to handle. The pie chart on the edge of a "table" shows the inserts to inserts + lookups ratio.
You can also see the traffic from a process' perspective.
