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
This would imply placing the actual amount of gas used in IsAuthorized and Refine alongside the WorkOutputs in each WorkReport.
Additionally, the number of segments imported, as well as extrinsic count and total size could be helpful.
There would be an additional portion of state, perhaps combined into $\pi$, which would record the Refine gas usage per-core and per-service asserting it to be used at the time of reporting and the Accumulate gas usage per-core and per-service asserting it to be used at the time of accumulation.
This may help diagnostic services since they won't otherwise be easily able to get at this information.
The text was updated successfully, but these errors were encountered:
gavofyork
changed the title
Consider: On-chain recording of Core gas usage & per-service breakdown
On-chain recording of Core gas usage & per-service breakdown
Mar 6, 2025
This would imply placing the actual amount of gas used in IsAuthorized and Refine alongside the WorkOutputs in each WorkReport.
Additionally, the number of segments imported, as well as extrinsic count and total size could be helpful.
There would be an additional portion of state, perhaps combined into$\pi$ , which would record the Refine gas usage per-core and per-service asserting it to be used at the time of reporting and the Accumulate gas usage per-core and per-service asserting it to be used at the time of accumulation.
This may help diagnostic services since they won't otherwise be easily able to get at this information.
The text was updated successfully, but these errors were encountered: