Benchmarking - Transaction bandwidth tests
We want to check how Hestia handles large numbers of transactions. This is easiest to do by adding a large number of small objects.
We can:
- Use redis as the backend - the file kv store will be too slow
- Use the SyncTool to sync a directory with a large number of files (e.g. the git checkout of hestia)
- Time the sync of the files. Also time copying them with plain 'cp -R' as a reference.
- Get the average transfer time per file (number of files/total time) and report it.
- Start looking for 'hot' or slow paths in the code - where is the code spending most time, what methods are called the most - this can be done with e.g. Gprof, which can be included in our cmake flags.