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
Opcodes: RET, BURN, MINT, SMO, LOG, LOGD, TR, TRO, RETD, RVRT, CALL; modifies receipts(usually add a new one). Each new receipt modifies BMT and slows down the addition of new receipts in the future. We need to update benchmarks to take that behavior into account.
Implementation details
Before running the benchmark for corresponding opcodes, we can fill the ReceiptsCtx with pre-defined receipts. The number of recipients should be realistic, and maybe we need to do some benchmarks to see the progression of the execution time. Without benchmarks maybe we can start with 100_000 or 1_000_000 receipts.
The text was updated successfully, but these errors were encountered:
Closes#1414. Also does some
upgrades for latest `fuel-vm` version. Targets
FuelLabs/fuel-vm#625 currently, needs new
`fuel-vm` release after that is merged.
This also mostly reverts #1457
which was not working correctly, especially with regards to `call`
instruction.
---------
Co-authored-by: xgreenx <[email protected]>
crypto523
added a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
ClosesFuelLabs/fuel-core#1414. Also does some
upgrades for latest `fuel-vm` version. Targets
FuelLabs/fuel-vm#625 currently, needs new
`fuel-vm` release after that is merged.
This also mostly reverts FuelLabs/fuel-core#1457
which was not working correctly, especially with regards to `call`
instruction.
---------
Co-authored-by: xgreenx <[email protected]>
Problem overview
Opcodes:
RET
,BURN
,MINT
,SMO
,LOG
,LOGD
,TR
,TRO
,RETD
,RVRT
,CALL
; modifies receipts(usually add a new one). Each new receipt modifies BMT and slows down the addition of new receipts in the future. We need to update benchmarks to take that behavior into account.Implementation details
Before running the benchmark for corresponding opcodes, we can fill the
ReceiptsCtx
with pre-defined receipts. The number of recipients should be realistic, and maybe we need to do some benchmarks to see the progression of the execution time. Without benchmarks maybe we can start with100_000
or1_000_000
receipts.The text was updated successfully, but these errors were encountered: