add benchmarks, initially for OcrdMets build/search #585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While developing #582 I wanted to know how the changes affect speed, so I set up a performance test on a typical METS file as it would be created by a sequence of OCR-D processors. In the test, METS with various numbers of pages is created and the
OcrdMets.find_filesandOcrdMets.add_filemethods are tested.We could benchmark different aspects of the code or even processors and workflows in the same vein. We could also make that part of our CI tests, maybe with a
benchmarkbranch that can be (force-)pushed to to create performance tests, possibly feeding the results to some service to see how throughput changes (hopefully: improves) over time.