Closed ramirezfranciscof closed 6 months ago
For repository development, it could be nice to know the distribution of filesizes and repo_size/nodes or total_files/nodes. Also maybe some information on the frequency of access to these files (and how often the same ones are accessed), but this could prove to be more difficult since its more of a "flow measurement" than a "state measurement".
Comments:
As a start one could write something that creates distributions from parsed output of the 'du' command.
It would interesting to know if users start to use the repository through other non related AiiDA tools. For a visual overview: On mac there is grandperspective http://grandperspectiv.sourceforge.net/ for linux and windows there are similar tools.
Also mentioning we started a very minimal tool here: https://github.com/ltalirz/aiida-statistics-query with @ltalirz - with a slightly parallel goal (getting statistics on the usage of AiiDA in published projects, getting at least the number of node types), but this could be a starting point
Currently there is verdi storage info
which gives a lot of information about storage contents. I am closing this for now. If there is additional information needed, a new issue can be opened.
This is an issue to discuss the possibility of adding a verdi command (
verdi stats
) so that the user can generate a text file with information of their AiiDA usage that developers could then use to make better informed decisions when improving the code. This originally came up when thinking how to design and test possible repository backends with @espenfl , and we noticed that even if we asked users for information on the size of their files they wouldn't know how to provide it, and even if they did it might be annoying to do.The idea would be to output all the gathered information in a machine-readable text file (json) that the user can inspect to check exactly what information he would be sending us (and thus these should never become gigantic intelligible walls of text). It would also be good to have this as a separate plugin, so when new information is needed, the plugin can be updated without needing to make an aiida-core release.
If any of you have ideas for what kind of information would give better direction to you development projects, please comment here.