Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add gas modelling numbers to FIP-0045 #523

Merged
merged 2 commits into from
Nov 15, 2022
Merged

Conversation

geoff-vball
Copy link
Contributor

I've added gas modelling numbers for all the calls affected by this FIP.

I want to flag that the increased execution cost for each verified deal is ~50M gas. For Prove Commit, this 50M increase is going to executed in cron. We already have issues with bounding cron execution. Would it make sense to add an addition fixed gas cost to prove commits with verified deals? I don't think the marginal cost increase is too big an issue to counteract to network issues that might arise from cron bloating even more.

It's probably too late to do anything about this for nv17, but something we may want to consider in a future network upgrade.

@arajasek
Copy link
Collaborator

Thanks for crunching the numbers, and opening this PR!

It's good to unearth that cron is going to get slower as a result of this change. The increase is relatively small relative to the total cron cost, but I think this makes it more important to evaluate ways to optimize cron. One possible optimization could be increasing the deferred proof verification cost for sectors that activate deals.

@anorth
Copy link
Member

anorth commented Nov 14, 2022

Thanks.

The flow of #298 will move deal activation always out of cron anyway. (We should still look to optimise it, of course).

FIPS/fip-0045.md Outdated Show resolved Hide resolved
Co-authored-by: Jiaying Wang <42981373+jennijuju@users.noreply.github.com>
@jennijuju jennijuju merged commit 385f069 into master Nov 15, 2022
@jennijuju jennijuju deleted the gstuart/0045-gas-modelling branch November 15, 2022 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants