LimitedWriter.write_le method is used to verify transaction sizes are below the minimum limit. Thus it makes sense to benchmark this method and the check_transaction method which encapsulates it.
This PR adds benchmarks of the following:
LimitedWriter.write_le and for transfer_public, transfer_private methods within credits.aleo
Benchmarks of both VM.check_transaction and LimitedWriter.write_le for a program called too_big.aleo that generates an execution transaction above 160kb.
Motivation
LimitedWriter.write_le
method is used to verify transaction sizes are below the minimum limit. Thus it makes sense to benchmark this method and thecheck_transaction
method which encapsulates it.This PR adds benchmarks of the following:
LimitedWriter.write_le
and fortransfer_public
,transfer_private
methods withincredits.aleo
VM.check_transaction
andLimitedWriter.write_le
for a program calledtoo_big.aleo
that generates an execution transaction above160kb
.Results (Mac OSX - M1 Max: 10-core CPU - Memory: 64GB)
Results
LimitedWriter
for transactions over the maximum are about 15% of the total runtime.LimitedWriter.write_le
for transfer_publics execution transactions (which are ~3kb) take %0.07 of the total runtime of the check_transaction check.