CPU usage seems off

[savikko]

Hi!

Starting the container, it connects successfully to supabase instance but it seems that CPU usage is not telling what it should tell:

So it seems to spike to 100% but that does not really happen, comparing to load:

Also, sometimes "basic cpu" goes to minus something:

[riderx]

It's not at 100% it's idle, the problem is before on previous version the value where constant and not missing some point as you can see there is some 0 point

[begank]

It's not at 100% it's idle, the problem is before on previous version the value where constant and not missing some point as you can see there is some 0 point

@riderx I Got the same problem (sometimes "basic cpu" goes to minus something),can you tell me how to resolve it? thank you so much

[riderx]

I don’t have a way to resolve it yet, but maybe i can ask on X

[pcnc]

Hi folks - just want to confirm some data points.

Is this running on Fly.io, or a dockerized setup? We have a theory that network latency might play a role in the discrepancies which are displayed - does reducing the scrape config to 45s down from 60s alleviate this?

[riderx]

@pcnc i changed it and did fly deploy and no better, updated at 13:04

honestly i'm not sure the config was update properly, i just don't want to loose all past data by deleting all

[riderx]

After a while i realized it did improve a bit, now the chart almost not stay at 0

[pcnc]

I see, thank you!
We've managed to reproduce the behaviour and are actively looking into this

[encima]

Note that this does not happen when self-hosting/using via docker. I self host grafana and prometheus. Using the default dashboard, the metrics look good when querying with a 60s refresh:

[riderx]

Also it was not happening in FLY.io last year, then with one update this started to happen

[encima]

This could also be scraping options configured to scrape more often. Docs on the Supabase site have been updated, as well as the README in this repo.
Let us know if it is still causing issues!