PDFOwl Renderer

PDFOwl PDF Rendering

Properties are available to configure the rendering of PDF documents to images.

The PDFOwl microservice uses a pool of dedicated PDFOwl rendering processes. Each PDFOwl process is started for a single document, and can processing a single query at the same time. For a given document, multiple PDFOwl processes can coexist simultaneously. The PDFOwl microservice recycles PDFOwl processes for a given document, until the pdfowl.client.ttl limit is reached. At most pdfowl.client.max-idle idle processes are kept for reuse: the oldest idle processes beyond this limit are stopped.

application.properties located in ARender-Rendition-2023.23.0/modules/PDFOwl

Description	Parameter Key	Default value	Type
Maximum duration of a rendition task to PDFOwl after which the watchdog will kill the PDFOwl process	pdfowl.client.watchdog	10000	Integer
Maximum duration of an idle PDFOwl process	pdfowl.client.ttl	30000	Integer
Memory ceiling hint for each PDFOwl process (in Megabytes), see below	pdfowl.memlimit.mb	(unset)	Integer
Enable recycling of PDFOwl processes	pdfowl.recycling.enable	true	Boolean
Maximum number of idle PDFOwl processes kept for reuse	pdfowl.client.max-idle	16	Integer

PDFOwl memory limit

pdfowl.memlimit.mb is passed to each PDFOwl process when it starts. PDFOwl derives its own hard memory limit from this value.

• When the property is not set, PDFOwl applies its own default memory limit. This is the recommended setting.
• Values above 2047 are capped to 2047, and a warning is logged.

Changed in 2023.23.0

Before 2023.23.0, the default value was 1024 and the limit was only applied once a document was open. If you set pdfowl.memlimit.mb=1024 explicitly, you keep a lower memory limit than the new default: remove the property unless you need to cap PDFOwl memory.