Increase in SNS Governance canister cycles consumption

We are seeing an uptick in daily burn of cycles of 2.6T on our governance canister. We aren’t doing many proposals so wondering why this is occuring?

1 Like

I’m seeing similar numbers for other governance canisters. This may be someone scraping data from these canisters. Is there something Dfinity can do here to change some of the calls to query’s or limit the cycle consumption on the SNS canisters?

1 Like

After CaffeineAI, lot of apps start calling into those governance canisters to get data (neuron holders). New SNS launches should be stopped/discontinued, running canisters under SNS will become lot more expensive.

Thanks for reporting this, we’ll take a look and try to explain what may have caused this increased cycles consumption rate for your Governance canister.

Do I read the graph correctly that the bump starts on July 11?

Its right after a governance upgrade.

3 Likes

Good catch, looks like this is pretty consistent across the governance canisters of different SNS DAOs.



1 Like

With https://dashboard.internetcomputer.org/proposal/137584 being adopted, the cycles consumption rate of SNS Governance should be normalized again. The identified cause was just a canister timer not being modulated properly (instead of once an hour, the cached metrics were recomputed one every 10 seconds).

Please monitor and confirm in the following days whether this solved the problem.

2 Likes

Thanks @aterga for getting to this so quick

1 Like