Hi, given that there is PDFBOX-5286, first noted in PDFBOX-5068, and we also see variations in performance between releases creating a testbed for performance testing came to my mind. I did some very basic tests using JMH some of which are note in above tickets.
What about formalizing that? Similar to testing done by the Tika colleagues when it comes to text extraction. Cases I see are around parsing, saving, rendering and text extraction and some basic workflows such as filling a form field. As runtime will differ between different environments it might be worth creating an extra subproject for that and run that as needed. We can take the numbers from the first run and create a baseline file from that if we'd like to have some kind of automated comparison... Having some common test will help us finding regressions earlier and also help testing enhancements against a defined set of files. This would complement the functionality based tests we have and also the larger test runs done for text extraction and rendering. WDYT? Maruan Sahyoun --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
