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
CodeCarbon does not actually provide any useful output:
Unless the user has one of the Intel monitoring tools installed the API defaults to a flat 50% CPU usage.
It uses CO2 Signal API behind the scenes, if it fails to retrieve a value it defaults to a fixed value taken from 2019!
We do not use 95% of the functionality, CC is designed to be hosted as a server, we do not need this.
The way we are currently using it is via the low level API which is not documented and likely to change frequently.
After looking into this I found it was a lot easier for us to do this ourselves. Not only that we can improve the measured values to be more representative by monitoring CPU percentage as we do already for resource metrics.
The text was updated successfully, but these errors were encountered:
Following on from #735
The text was updated successfully, but these errors were encountered: