Performance Comparison Graph

Test Description: Nested tables spanned over 500 pages.
Why is this important: Tables are layout elements that are very used in large documents like invoices, statements and product catalogs. It is mandatory for a renderer to be able to process them quickly, with minimum memory consumption. Nested tables are even more difficult to process, because some content can't be discarded until a row's layout is complete. Engines should be able to do this at page level because keeping the whole structure in memory will cause the formatting to fail as the number of pages increases.

Test XSL-FO files: Benchmark1.zip, Benchmark2.zip.
Generated PDF:    Benchmark1.pdf, Benchmark2.pdf.

Test Description: Rendering small documents on multiple threads.
Why is this important: This tests an engine's ability to handle multiple simultaneous requests. In concurrent usage scenarios (like websites) it is highly desired to be able to process as many requests as possible, in the shortest time, using as little memory as possible. We've tested all engines by simulating 10 and 100 simultaneous clients.

Test XSL-FO file:   Benchmark3.zip.
Generated Code:  BenchmarkSrc3.zip.
Generated PDF:    Benchmark3.pdf.

Test Description: Auto table spanned over 500 pages.
Why is this important: This tests an engine's ability to process tables whose layout is set depending on their content. Processing this type of tables will use up more system resources due to the extra operations being performed and the need to load the table's contents into memory. An engine must minimize the amount of resources required to perform these extra operations to be able to handle automatic tables in a production environment.

Test XSL-FO files: Benchmark4.zip.
Generated PDF:    Benchmark4.pdf.