PRODUCTION SPEED

Run batches in parallel

Keep deadline-driven runs moving: render independent jobs in parallel and reuse cached output when inputs haven’t changed.

Illustrative stacks of consistent documents beside a print stationILLUSTRATIVE CONCEPT
HOW IT WORKS

What this changes in your workflow

Independent files can render as parallel jobs. The cache lets an unchanged input reuse a previous result. Use the elapsed time in the job report to see where generation takes time on your own files.

  • Run multiple jobs in parallel.
  • Reuse output for unchanged inputs with caching.
  • Record elapsed time in the structured job report.
BUSINESS BENEFITS

What it means for your operation

  1. Finish more independent jobs inside the production window

    Run separate editions or reports together. A large file can render in parallel with smaller ones instead of holding the whole queue.

  2. Avoid rebuilding work you can reuse

    Keep unchanged outputs from the previous run when the cache applies. Spend compute and production time on the editions that changed.

  3. Measure both fresh and repeat runs

    Track the time until the last approved PDF is ready, cache reuse and output volume. Compare like-for-like batches and log proofing and delivery time separately.

ILLUSTRATIVE SCENARIOS

How industries can use it

Retail

Refresh regional price lists

Generate each region’s edition as an independent job. If only one region’s source changes, unchanged inputs can reuse cached results.

In the proof: Change one region’s prices in a test and confirm only the intended edition is different.

Explore retail
Manufacturing & distribution

Rebuild a catalogue by product family

Prepare a separate file for each product family. Run those files together, then carry forward the unaffected outputs when one family is revised.

In the proof: Include a dense catalogue section in the test and verify the dated edition labels.

Explore manufacturing & distribution
Logistics & operations

Produce reports across depots

Run separate depot summaries in parallel so a large depot report does not need to finish before other independent documents begin.

In the proof: Compare a normal depot and one with a long table. Use the report to distinguish render time from time spent reviewing and delivering files.

Explore logistics & operations
FIRST-PROOF CHECKLIST

Test it on a document you already print

Start with an anonymised example and record what the finished file must do before the job moves to the next stage.

  1. Choose representative files. Include the shortest, longest and most image-heavy items from the batch.
  2. Compare two builds. Measure a fresh render and a repeat with caching. Change one input and record which outputs must be regenerated.
  3. Check output as well as elapsed time. Review document counts, representative PDFs and warnings. Measure delivery separately if it is part of the workflow.
MARQIUS FEATURES

Related capabilities

All features
Illustrative printed letters with differing data fields
VARIABLE DATA

Personalise the next set of PDFs

Use one approved layout and a fresh set of records to prepare statements, correspondence and other documents that vary from recipient to recipient.

Explore feature
Two proof pages under inspection with a print loupe
RELIABILITY

Catch issues before the handoff

Use press checks and page-level findings to review the file before release. Strict mode can stop a run when a check raises a warning, so the next step starts with a decision.

Explore feature
Illustrative job tickets, production folders and output proofs arranged by stage
WORKFLOW HANDOFF

Track jobs and route completed files

Follow a recurring run from the current data to the finished PDF. Agree where the result should go and what to review when a job needs attention.

Explore feature

Bring a document your team already makes.

Tell us how it’s produced today and what you need from the next run. We’ll discuss a representative proof.

Discuss a Sample
QUESTIONS & ANSWERS

Parallel PDF Batch Processing and Caching: frequently asked questions

What kind of job benefits most from parallel processing?

A run made up of independent files, such as regional lists or separate depot reports. A single long document is still one job.

What happens when a document changes between builds?

The changed input should be rendered again. Test your cache with both a changed file and an unchanged file before relying on it in production.

Do generation timings include physical printing?

Use the job report to measure document generation. Paper handling, printing and delivery are separate steps to measure in your workflow.