Is your feature request related to a problem? Please describe.
It can be hard for managers to value the sustainability impact of bad practices
Describe the solution you'd like
Even if we miss some context during static code analyses, it would be nice to provide some estimations
- at minimum in kW or joules
- if possible with a CO2 estimation
- at best including other metric estimations such as water
Additional context
For each Creedengo rules, the Green Code Initiative started to provide measurements of the gains the aims to provide. This would give an indicator for each time this piece of code is executed.
In Cast Highlight, provides a CO2 estimation. In their context, they ask the user to fill a form including informations about the project which can help for the estimation. More details in this document
Fruggr offers an option to import matomo or google analytics helping the tool to understand which analysed pages are the most often called and then calculated a more accurate footprint
NewRelic, thanks to the metrics they gather, provides a VScode extension showing which functions have the biggest performance impact in production.
So in short we should probably:
- First provide a "per issue" execution footprint estimation
- Add a user filled form to give a more global application level estimation
- Support analytics imports (or API access) to result in a more accurate result
Is your feature request related to a problem? Please describe.
It can be hard for managers to value the sustainability impact of bad practices
Describe the solution you'd like
Even if we miss some context during static code analyses, it would be nice to provide some estimations
Additional context
For each Creedengo rules, the Green Code Initiative started to provide measurements of the gains the aims to provide. This would give an indicator for each time this piece of code is executed.
In Cast Highlight, provides a CO2 estimation. In their context, they ask the user to fill a form including informations about the project which can help for the estimation. More details in this document
Fruggr offers an option to import matomo or google analytics helping the tool to understand which analysed pages are the most often called and then calculated a more accurate footprint
NewRelic, thanks to the metrics they gather, provides a VScode extension showing which functions have the biggest performance impact in production.
So in short we should probably: