Tracking Issue for Benchmarks

[hinto-janai]

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter.

What

This is a tracking issue for integrating initial benchmarking code for Cuprate as described in #193.

Steps

N/A = not applicable (the crate in question does not benefit from micro benchmarking).

• Initial proposal: Formalizing benches/ #193
• benches/ initial setup: benches: initial implementation #196
• Move to Cuprate/benches: Remove /benches #354
• Criterion benchmarks
  • cuprate-fast-sync
  • cuprate-consensus
  • cuprate-consensus-rules
  • cuprate-consensus-context
  • cuprate-constants: N/A
  • cuprate-cryptonight: criterion: initial benchmarks #352
  • cuprate-helper: criterion: initial benchmarks #352
  • cuprate-epee-encoding
  • cuprate-fixed-bytes
  • cuprate-levin
  • cuprate-wire
  • cuprate-p2p
  • cuprate-p2p-core
  • cuprate-dandelion-tower
  • cuprate-address-book
  • cuprate-blockchain: criterion: initial benchmarks #352
  • cuprate-database: criterion: initial benchmarks #352
  • cuprate-database-service
  • cuprate-txpool
  • cuprate-pruning
  • cuprate-test-utils: N/A
  • cuprate-types: N/A
  • cuprate-json-rpc: benches: initial implementation #196
  • cuprate-rpc-types: criterion: initial benchmarks #352
  • cuprate-rpc-interface: N/A