


Should we export execution traces (default: true) Read and write syscall results from datastore Set the repo directory for the lotus bench run (defaults to /tmp)
#Taks benchmark tests verification#
Set the parallelism factor for batch seal verification (default: 4) Halt validation after given height beware that chain traversal by height is very slow (default: 0) Start validation at given height beware that chain traversal by height is very slow (default: 0) Genesis tipset key in format cid1,cid2,cid3… Halt validation at the given tipset key in format cid1,cid2,cid3… Start validation at the given tipset key in format cid1,cid2,cid3… Pass miner address (only necessary if using existing sectorbuilder) (default: “t01000”).īenchmark chain import and validation using lotus-bench import command. Skip the unseal portion of the benchmark (default: false)īenchmark a proof computation using lotus-bench prove. Skip the commit2 (snark) portion of the benchmark (default: false) Output results in json format (default: false) Pass a directory to run post timings on an existing sectorbuilder Pass miner address (only necessary if using existing sectorbuilder) (default: “t01000”) 32GiB (default: “512MiB”).ĭisable gpu usage for the benchmark run (default: false). Path to the storage directory that will store sectors long term (default: “~/.lotus-bench”). Verify window post proof (hot): 1.517569ms Verify window post proof (cold): 8.572963ms Verify winning post proof (hot): 1.26867msĬompute window post proof (cold): 446.549819msĬompute window post proof (hot): 450.785891ms Verify winning post proof (cold): 17.949129ms version, -v print the version (default: false)īenchmark a sealing computation using lotus-bench sealing. Help, h Shows a list of commands or help for one command Import Benchmark chain import and validation Sealing Benchmark seal and winning post and window post Lotus-bench - Benchmark performance of lotus on your hardware Use the self-documenting feature of the tool to explore the different commands./lotus-bench -help You can now run lotus-bench against your system. This will produce a lotus-bench binary in the current folder. Go run /GeertJohan/go.rice/rice append -exec lotus-bench -i. lotus-worker /usr/local/bin/lotus-workerĬall make lotus-bench to build the Lotus benchmark binary: make lotus-bench Rm -rf build/.filecoin-install build/.update-modules lotus lotus-miner lotus-worker lotus-shed lotus-gateway lotus-seed lotus-pond lotus-townhall lotus-fountain lotus-chainwatch lotus-bench lotus-stats lotus-pcr lotus-health lotus-wallet testground If you just cloned the repository or have misplaced the lotus binary, build the project: cd ~/lotus

The lotus binary must be built and within the ~/lotus repository folder. If you do not have an existing copy of the repository, clone it from GitHub: git clone ~/lotus You must have the Lotus repository on your computer.
