:wave: Can somebody explain why the heartbeat consumes so much cycles, even when the function body is empty it burns through 3_000_000 on every beat. Just a explainer what i am trying to do / how i set it up; I am trying to set up self-sustaining canisters-system where each canister can request c…

Honestly I think a way to create custom heartbeats should be provided by default by the ICP, its a feature needed for many use cases and in my opinion we shouldn’t rely on a 3rd party service that has to be trusted and somehow funded to do something so basic.

[image] Zane: has to be trusted and somehow funded to do something so basic That is exactly the spirit of open services. Why shun away from it?

Because in my opinion having to pay to use a basic feature like custom heartbeats is just stupid, the fact its not offered by the “framework” by default and we as a community have to gather and discuss how and who will implement it even more, it looks really bad from an outside perspective. Like ima…

What’s the difference between that and any other feature of the IC? You pay to compute. It costs X cycles to store a value in stable64 memory, it costs Y cycles to call the management canister, it costs Z cycles to call the (community provided) cron canister. Computation as a service is the entire m…

The difference is you pay cycles for what you actually use be it computation or storage, if I want to run a function once every 24 hours and I have to pay for useless calls every second, that is stupid. If it were a very niche use case then I’d agree with you, but this is something lots of dApps nee…

[image] Zane: The difference is you pay cycles for what you actually use be it computation or storage, if I want to run a function once every 24 hours and I have to pay for useless calls every second, that is stupid. So who’s gonna pay for keeping track of the schedules?

Ideally nobody, it should be part of the protocol, wouldn’t it be better performance wise to have a system level canister (or more not sure about scalability requirements) take care of scheduling instead of having hundreds of user level ones wasting CPU cycles every second for no reason?

[image] Zane: instead of having hundreds of user level ones wasting CPU cycles every second for no reason? I think a lot of people agree that a better solution needs to be available for working with heartbeat functionality. The difference in opinion seems to be regarding who gets to design, b…

I agree but I’d like if progress were a bit quicker cause while we discuss on what’s the better approach, who’s going to do it and how is it going to be funded, there are devs who need the feature and either have to pay more than they actually use or wait for a solution to be released, whenever that…

If your goal is quick progress at the expense of the best solution, that is a goal built for community-made canisters. Those can be iterated upon and refined. But to embed something in the protocol is to make a serious support commitment; it has to be the version developers can use for everything an…

Cycle burn rate heartbeat

Developers

ulan July 7, 2022, 1:51pm 46

FYI: Heartbeat improvements / Timers [Community Consideration]

Topic		Replies	Views
Heartbeat getting called before init is finished Developers	24	1743	April 26, 2022
Why does a canister keep consuming cycles? Developers community-consideration	19	2053	March 11, 2022
Calculate an estimate of cycles consumption: a universal example Developers	28	2753	May 25, 2022
IC Cron - let's schedule some tasks bois Developers	26	3240	February 12, 2022
Heartbeat improvements / Timers [Community Consideration] Developers community-consideration	142	9370	October 17, 2024

Cycle burn rate heartbeat

Related topics