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
Currently, the models available in CO2.js are frontend focused, with a bias towards estimating website carbon emissions. We would like to see additional models that can be used for other areas of digital emissions estimation added to CO2.js.
One area that we believe could benefit from this is the estimation of server-side emissions. We believe that having a simple implementation that can estimate the emissions of running some code on a server would be extremely useful for developers. We have seen some implementations of this in other languages. Most of the libraries listed in the recent GitHub blog post on sustainable software tools do this in some way.
This issue is to discuss what an implementation might look like in CO2.js. It might be a lite version of Cloud Carbon Footprint, or some other existing methodology. It might be a wrapper around some other tooling or library that we can include as a dependancy. It might simply be a reference model that takes some basic inputs (e.g. server model, usage duration, used capacity) and returns a result - this again would have to be based on some existing model.
This work would tie in closely with making CO2.js extensible by converting it to a plugin-based architecture as outlined in #206.
The text was updated successfully, but these errors were encountered:
Hi there,
I'd like to work on this one. I have experience using Kepler to obtain energy used by k8s pods and translate into emissions calculations, not with Cloud Carbon Footprint, though.
In regards to the plugin system I'd also like to discuss about it, if still pertinent.
I'm also open to have a chat on any digital channel, if available.
Currently, the models available in CO2.js are frontend focused, with a bias towards estimating website carbon emissions. We would like to see additional models that can be used for other areas of digital emissions estimation added to CO2.js.
One area that we believe could benefit from this is the estimation of server-side emissions. We believe that having a simple implementation that can estimate the emissions of running some code on a server would be extremely useful for developers. We have seen some implementations of this in other languages. Most of the libraries listed in the recent GitHub blog post on sustainable software tools do this in some way.
This issue is to discuss what an implementation might look like in CO2.js. It might be a lite version of Cloud Carbon Footprint, or some other existing methodology. It might be a wrapper around some other tooling or library that we can include as a dependancy. It might simply be a reference model that takes some basic inputs (e.g. server model, usage duration, used capacity) and returns a result - this again would have to be based on some existing model.
This work would tie in closely with making CO2.js extensible by converting it to a plugin-based architecture as outlined in #206.
The text was updated successfully, but these errors were encountered: