diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2022-09-01 00:40:15 +0200 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2022-09-01 22:15:54 +0200 |
| commit | 4f4b908605a0c0e9cf3fc568302b074801eb7419 (patch) | |
| tree | 57a47a647569cff6456bcf6e050998a2edc4c675 /TODO | |
| parent | 3d029fb17ef6b8ea9094394741f103608f698bad (diff) | |
| download | qpdf-4f4b908605a0c0e9cf3fc568302b074801eb7419.tar.zst | |
Add a file with arrays with lots of nulls to the test suite
A bug was fixed between qpdf 8.4.2 and 9.0.0 regarding this type of
file (see #305 and #311), but it was necessary to retest after some
major refactoring work at the lexical and parsing layers. This lays
the groundwork for including this in performance benchmarks and in the
qpdf test suite rather than having to keep a large,
non-redistributable file around.
20 arrays of 20K nulls is plenty for performance memory testing and
doesn't take too long to run. Compared to qpdf 8.4.2, in qpdf 11.0.0,
the file generated here uses 3% of the RAM and runs over 4 times
faster.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -7,9 +7,9 @@ Before Release: * Review in order #726 * Make ./performance_check usable by other people by having published files to use for testing. - * https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf -* Incorporate --report-mem-usage into performance testing. Make sure - there is some test somewhere that exercises the millions of nulls case. + * Site https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf + * Incorporate --report-mem-usage into performance testing. + * Include output of test_many_nulls * Evaluate issues tagged with `next` * Stay on top of https://github.com/pikepdf/pikepdf/pull/315 |