We were using 'x'*size as payload, but on real usage the payload will be random. This commit randomizes the payload using a predefined seed, so the random payload will be the same across benchmarks. Using random payloads also improves accuracy of compression or encoding impacts and we will be evaluating those changes for resouce usage issues. Also note that base64 is used on payload. That was needed for utf8 safety, but overhead was removed to leave payloads as defined by benchmarks. Base64 was chosen also due its popular usage on MIME encoding, which is used on mail attachments (our current scenario).
This isnt a test, but a benchmark. Initialization sounds more like an operation while instance is just something.
We are using lower values on test_encdecpool due high memory usage, described in #7370. Added a comment to explain it.
defer parameter wasnt clear
Otherwise it will add unrelated overhead to results.
They arent used so far and using empty dicts to make them work is ugly. Removing it leaves the return function on setup code clean and readable.
1000 docs at 100k~500k are exploding memory (4Gb+4Gb swap). Changed for 100 docs in order to be able to get measures on higher loads. Now its 10k, 100k and 500k
Hypothesis: raw vs doc Added the same sizes set (10k, 100k, 500k, 1M, 10M, 50M) as the document crypto test, so we can compare how close to raw the higher level operation is.