The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →To create 1,000 separate PDFs with jsreport, submit 1,000 report requests to a template using the chrome-pdf recipe, keep concurrency bounded by the capacity of your jsreport server, and measure a representative batch before estimating the full run. Each worker handles one request at a time; extra requests wait in the queue. More workers can increase total batch throughput, but they do not make an individual report render faster. There is no reliable completion-time estimate without knowing your template, data, machine limits, and configuration.
First, define what “1,000 PDFs” means
This guide assumes you want 1,000 report requests to produce 1,000 individual PDF files. That differs from producing one PDF containing 1,000 pages. Page count, data volume, images, and template complexity all affect rendering, so a test on one short report does not necessarily predict a batch of long reports.
Do not use jsreport’s published historical benchmark as a direct estimate for this job. It submitted 1,000 parallel requests, but each request rendered a 100-invoice, 100-page report. That is a different workload from 1,000 separate one-page reports, and it was run on older hardware. The figures and conditions are detailed below.
Set up and validate one representative report
Before starting a batch, configure a template to use the chrome-pdf recipe and render a report that resembles the reports you will actually generate. Chrome PDF prints HTML through headless Chrome. Confirm that the PDF’s content and pagination are correct before increasing request volume.
#1 Best Overall
- INNOVATIVE CARTRIDGE-FREE PRINTING — No more dealing with lots of tiny ink cartridges; With this wireless document and photo printer each ink bottle set is equivalent to about 90 individual cartridges²
- LESS FREQUENT INK REPLACEMENT — Replacement ink bottles don't have to be changed nearly as often as ink cartridges¹; When you choose this combination printer, scanner and copier you can print up to 4,500 pages black/7,500 color³
- COLOR PRINTING — Up to 2 years of ink in the box4 (and with every replacement ink set) for fewer out-of-ink frustrations
- ZERO CARTRIDGE WASTE — By using an Epson EcoTank printer you can help reduce the amount of cartridge waste ending up in landfills
- HOME PRINTER DESIGNED FOR RELIABILITY — The Epson EcoTank ET-2800 All-in-One Supertank Color Printer creates vivid, detailed prints and documents thanks to Micro Piezo Heat-Free Technology; Fire off 10 ISO pages per minute1 to easily finish large jobs
Check output-affecting settings
The recipe supports settings including paper format or explicit dimensions, page ranges, margins, print media behavior, headers and footers, and options for waiting on JavaScript or network activity. Settings can be stored with the template or supplied through template.chrome. Exact labels and behavior can vary by installed jsreport release; check the documentation for the version you run at jsreport Chrome PDF documentation.
- Page geometry: Verify format or width and height, margins, orientation where applicable, and any page range.
- Print styling: Check media type and print-specific CSS. A page that looks right on screen may paginate differently in print.
- Dynamic content: If JavaScript populates the report, ensure capture waits for the relevant work. Use a wait option only as needed; an unnecessarily long wait adds time to every request.
- Fonts and assets: Confirm that fonts, images, and other resources load in the rendering environment. Missing or delayed assets can change layout or leave gaps in the PDF.
- Headers and footers: Validate their appearance and spacing against the printable area.
Use realistic data, including unusually long text or records that expand beyond the typical page. A representative test should expose layout changes, slow assets, and oversized output before those issues are multiplied across hundreds of requests.
Bound concurrency and measure the batch
jsreport’s worker count controls request concurrency: a worker processes one request at a time, and incoming requests wait when all workers are busy. Worker count is not a per-report speed setting. Increasing it may allow more independent reports to render simultaneously, but it can also raise CPU and memory pressure.
- Choose a modest client-side concurrency limit. Do not launch all 1,000 requests at once by default. Keep the number of in-flight requests within a bounded level appropriate to the server’s configured workers and available resources.
- Render a representative sample. Include typical reports and the largest or most complex cases. Record elapsed time, failures, output sizes, CPU and memory behavior, and how many requests are waiting.
- Change one capacity setting at a time. Compare bounded concurrency levels and, if relevant, worker or Chrome allocation settings. Use the same sample and template mix for each run.
- Recheck at the intended operating level. A short sample can conceal memory growth or a queue that builds up over a longer batch. Observe the system for long enough to see sustained behavior.
- Estimate cautiously. Use measured results from reports like yours, then validate against the full job or a larger staged run. Do not multiply a single-report time by 1,000 and treat it as a dependable schedule when reports run concurrently.
The documentation does not establish a universal worker count or client concurrency value for 1,000 reports. The useful setting is the one that improves total throughput for your own workload without causing resource saturation, errors, or unacceptable output delays.
Find the bottleneck before adding capacity
jsreport’s Chrome PDF performance guidance says: “First, make sure the chrome-pdf recipe is the bottleneck by checking the studio profile tab.” Use the Studio profiler before changing workers or Chrome allocation. A slow batch may be limited by template execution, data preparation, network access, or another part of the reporting pipeline rather than PDF generation itself.
Rank #2
- CARTRIDGE-FREE PRINTING — Print lab-quality photos, graphics and creative projects; Get vibrant colors and sharp text with Epson's high-accuracy printhead and Claria ET Premium 6-color inks
- INK BOTTLES — Save on photos1 and creative projects with affordable in-house printing; All-in-one printer allows you to print 4" x 6" photos for about 4 cents each vs. 40 cents with traditional ink cartridges1
- LESS FREQUENT INK REPLACEMENT — Replacement ink bottles don't have to be changed nearly as often as ink cartridges¹; Printer, scanner and copier lets you print up to 6,200 color pages³
- PRINT FOR LONGER — Up to 2 years of ink in the box² (and with every replacement ink set) for fewer out-of-ink frustrations with this wireless printer
- ZERO CARTRIDGE WASTE — Epson EcoTank printer helps reduce the amount of cartridge waste ending up in landfills; Cartridge-free printer uses high-yield ink bottles; Each replacement ink bottle set is equivalent to about 100 individual ink cartridges⁴
If rendering is the bottleneck
Inspect expensive page content and isolate elements that are costly to render. Large images are a common thing to check: an image can contain substantial data even when CSS displays it at a small size. Verify source dimensions and payload rather than assuming the visible size reflects the amount of work or PDF data involved.
For very long reports, jsreport’s guidance notes that splitting a report into smaller parts and combining them can be an option in suitable cases. That is a design trade-off, not a universal fix: it can change how page breaks, headers, and shared content behave, so validate the combined result against the intended document.
Choose Chrome process settings based on evidence
Chrome allocation and reuse are configuration choices, not automatic accelerators. The current recipe documentation describes a default setup that allocates and reuses Chrome instances per worker thread, as well as alternatives such as increasing instances per thread for nested-report workloads, using a dedicated-process strategy, or connecting to an existing remote Chrome instance. Confirm exact options and defaults for your installed jsreport version in the recipe documentation.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Starting a Chrome process costs roughly 100 ms according to the documentation. That overhead is one reason a fresh process for every report should not be assumed to improve overall performance. Compare process strategies using your own workload, and consider both throughput and resource use. Nested reports may have different needs from a straightforward queue of independent documents.
Save the outputs and make failures recoverable
For a 1,000-file job, treat each report as an independently tracked unit of work. These are general batch-processing practices rather than jsreport-prescribed queue or storage settings:
Rank #3
- SET IT UP ONCE AND PRINT WITH CONFIDENCE. No complicated maintenance. Just easy, reliable printing you can count on.
- INK FOR YEARS. NOT MONTHS. Up to 2 years of ink included. Get thousands of pages of cartridge-free printing. More pages, less hassle
- KEEPS PRINTING WELL AFTER COMPETITORS HAVE QUIT. No complex maintenance. Sharper text, richer colors.[2] Only with HP Smart Tank
- PREMIUM SUPPORT - Strong technical expertise to solve issues faster
- THE LAST PRINTER YOU'LL EVER NEED. Enjoy years of refillable, cartridge-free printing.
- Assign every report a stable identifier and derive a deterministic output name from it, so a retry does not silently overwrite a different report.
- Record each request’s status and output location. Distinguish completed, failed, and still-pending items rather than relying only on a final batch-level success message.
- Retry only failed items according to your application’s policy. Avoid blindly resubmitting the entire batch after a partial failure.
- Check that each expected file exists, is nonempty, and can be opened as a PDF. If correctness matters, also validate representative pages and content rather than treating file creation alone as proof of a correct report.
- Retain enough job information to reconcile the input set with the output set and identify missing or duplicated reports.
For operational visibility, monitor CPU, memory, request errors, queueing, and output volume while the batch runs. If the host or container has strict CPU or memory limits, include those limits in the benchmark; results from an unconstrained machine will not predict a constrained deployment.
What the published benchmark does—and does not—tell you
In a historical article published by jsreport around 2014, the team reported 641 PDF pages per second and a total rendering time of 156 seconds for 1,000 parallel requests. Each request rendered a 100-invoice, 100-page report with a 250 KB PDF output. The test machine was an Intel Core i7-2600K at 3.4 GHz with four cores and 16 GB of RAM; reported memory consumption was 1.5 GB. See jsreport’s benchmark article.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsThose numbers describe that particular test, not a present-day capacity guarantee. They are not a measurement of 1,000 separate one-page reports, and they do not establish a hardware recommendation or completion time for your template. Treat them as historical context only. For a useful comparison, record the sample size, page counts, output sizes, jsreport version, machine or container limits, worker count, and Chrome allocation settings alongside your own results.
Or skip the browser setup
ScreenshotNeo is a separate website screenshot API, not a replacement for jsreport’s HTML-to-PDF report workflow. It can be useful when the task is capturing a webpage as an image; it does not turn this jsreport batch into 1,000 generated PDFs. For that separate screenshot use case, one GET request can return an image or PDF:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes supported cookie and consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. It also offers an MCP server for AI agents. The free plan includes 1,000 screenshots per month without a card, and paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up free for 1,000 screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common batch problems
Requests queue longer than expected
When all workers are occupied, new requests wait. Check whether the configured worker count and client concurrency are aligned with available capacity. Raise concurrency only after observing CPU, memory, error rates, and total throughput; a larger queue does not itself make reports finish sooner.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #4
- Wireless Bluetooth Printer: Portable thermal printer compatible with iPhone, Android phones, iPad and tablet computers via Bluetooth. For smartphones, please download the "Nada Print" App. You can also connect to laptops and computers for printing using a USB-C cable. (Note: Laptops and computers can only be connected via USB and require the installation of a driver first. Bluetooth connection is not supported.)
- No-ink printing: Only supports US Letter and A4 size thermal paper.(Doesn't support regular paper) The no-ink portable thermal printer uses direct thermal technology, requiring no ink, toner or ribbons, making it environmentally friendly, cost-effective and time-saving. The thermal printer package comes with a roll of US Letter thermal printing paper. Note: When installing the paper, remember to switch the paper size switch on APP
- Clear Print: NDYIN N80 portable thermal printer adopts high-definition printing technology, with a 203DPI resolution to provide you with clear printing results. This mobile printer is compatible with roll paper, folded paper and tattoo transfer paper, supporting printing from your mobile phone PDF, Word, pictures and web pages anytime and anywhere. It is recommended to use our NDYIN thermal paper to achieve good printing quality
- Portable wireless printer for travel: The thermal printer is equipped with a built-in 1500mAh rechargeable battery, which can print 160 sheets of 8.5" x 11" thermal paper after being fully charged. It weighs only 1.5 pounds and is compact in size. This ink-free portable printer can be easily carried in a backpack or briefcase! It is perfect for business travel, cars, small offices, construction sites, schools and homes. You can print documents, contracts, invoices and boarding passes anytime and anywhere
- The N80 thermal printer has a wide range of uses. The package includes the N80 printer, a roll of US Letter paper(7m/roll), a user manual, a guide card, a type-C soft cable and a type C adapter. Note: The charging adapter is not included. Special thermal paper is required for use; ordinary paper cannot be used. This ink-free portable thermal printer is suitable for various scenarios such as home, school, travel, office, and outdoor, meeting the printing needs of different groups of people. This tattoo template printer is also compatible with tattoo transfer paper, making it an ideal choice for tattoo art
Adding workers does not improve elapsed time
The bottleneck may be inside each report, in data preparation, or elsewhere in the pipeline. Check the Studio profiler to establish whether chrome-pdf is the limiting step. If it is, investigate page content and assets before changing worker count again.
PDFs are missing images, fonts, or dynamic content
Check that resources are reachable from the rendering environment and that the template waits for the work needed to produce the page. Review the relevant media and wait settings, then render a representative report and inspect the resulting PDF. Do not add a fixed wait without checking whether it addresses the actual missing resource or timing issue.
Memory use or failures rise during a long run
Compare a sustained sample with a short test, monitor the host or container’s actual limits, and review report size and page content. Check the installed jsreport release’s Chrome reuse and allocation configuration. A user-reported memory issue on jsreport 4.12.0 in Docker is not enough to establish a general product defect; investigate your own version and environment rather than assuming the same cause.
The batch is slower after changing Chrome strategy
Process startup has overhead, and allocation choices can change resource contention. Revert to the prior known configuration, then compare strategies under the same sample and concurrency. Keep the version-specific configuration documented so a later change can be evaluated against a reliable baseline.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
