You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GraalVM Dashboard tool has a lot of potential as diagnostics tool.
Since there is currently no way to log issues/feature requests for the Dashboard, I want to open this discussion to use as a point of contact to get feature requests to the Dashboard team, and get an overview of what may be lacking to make Dashboard a usefull diagnostics tool for your use case.
To get things started:
1. Better way to browse through included sources
This is something the Dashboard team is already looking into (@alina-yur)
Currently, it is dificult to find specific classes or methods in the code size breakdown. It would be useful to be able to browse through the content of the native image much like you're browsing through code. So you can browse to a specific package, get the info, see which classes are included of that package, the methods of the classes etc in one big treeview instead of the current block view.
A great example of a different tool that implements such an overview, in this case for your entire disk content, is WinDirStat.
2. Browse through included resources
The heap size breakdown shows byte arrays as greatest contributor to the heap size. This includes all resources (and possibly resource bundles?), but there is no way to tell what these resources are and what their contribution is to the image size. It would be nice to get a browseable overview of this as well.
For the required additional dashboard dump info, there's this issue: #3648
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The GraalVM Dashboard tool has a lot of potential as diagnostics tool.
Since there is currently no way to log issues/feature requests for the Dashboard, I want to open this discussion to use as a point of contact to get feature requests to the Dashboard team, and get an overview of what may be lacking to make Dashboard a usefull diagnostics tool for your use case.
To get things started:
1. Better way to browse through included sources
This is something the Dashboard team is already looking into (@alina-yur)
Currently, it is dificult to find specific classes or methods in the code size breakdown. It would be useful to be able to browse through the content of the native image much like you're browsing through code. So you can browse to a specific package, get the info, see which classes are included of that package, the methods of the classes etc in one big treeview instead of the current block view.
A great example of a different tool that implements such an overview, in this case for your entire disk content, is WinDirStat.
2. Browse through included resources
The heap size breakdown shows byte arrays as greatest contributor to the heap size. This includes all resources (and possibly resource bundles?), but there is no way to tell what these resources are and what their contribution is to the image size. It would be nice to get a browseable overview of this as well.
For the required additional dashboard dump info, there's this issue: #3648
Beta Was this translation helpful? Give feedback.
All reactions