Everything goes fast in the beginning (after a reboot). Then I can generate PDF-files and store them on disk fast.
But after a couple of, it goes very slow. It goes from about 1 second per PDF to 10 seconds per PDF.
I didn’t have this issue before. It just came from nowhere. Any ideas? Any logfiles to check?
Memory and CPU is not the issue, between 20% - 40% utilization when running.
Version 2022.1
Windows Server 2019
12 CPU
48GB RAM
Anything else running on that system other than the obvious? (Workflow, Connect, OS)
How are you generating the PDF? Connect? PP7 form? CreatePDF plugin?
If Connect, are all PDF created the same job size?
Hi, nothing else is running on the server. We installed a gitlab runner on it but that’s not running yet.
As this was kind of urgent, I configured a new Windows Server 2022 and installed Connect 2023.1 on it. Now it has been running for a bit longer time than it took on the previous server to get performance issues.
I will give it another day or two and see if it is working in the new environment.
I generate the PDFs through Workflow, using the all in one plugin and store PDF to disk or email them with Sendgrid.
No, every job is unique and as it size, but most of them are just 2 pages.
Without access to the workstation I’d say one of the following but your best bet is to open a technical support ticket via our website:
If I get the same issues on the new server, I will open a ticket.
I use only 1 Weaver Engine and 1 DataMapper Engine. I use 8 Merge Engines though.
Maybe we have something here. I will try to use the following instead:
1 Datamapper Engine
5 Merge Engines
5 Weaver Engines
Does above sound good to you?
I have tried disabling Antivirus completely, and it is the same.
I will try to set all big workflow process to self replicating, today only the biggest one is self replicating.
The number of Merge engines wouldn’t matter much as it is what “merge” your data with your Template. It is also sends HTML emails and creates webpages. There are no limitation for that engine (other than the available system resources 
).
However, your Weaver engine is what creates the PDF. So why not go right away with the maximum of 8?
As for setting all big Workflow’s processes to self-replicating, there are consequences. Self-replication is not a boost, if there is only one file, it will not go faster. Only use it when you have mutliple files coming at once and you want them handled in parallel.
Also know that if you put too many processes in self-replication, then your Connect Server might besome your bottleneck.
A balance is always the best. Check how many jobs come during period of your day and see if they can all be handle simultaneously. Should you find out that there are too many for the Connect Server to handle simultaneously, you might consider upgrading to PReS Connect Server where you can run 64 jobs in parallel.
A good reading is Engine configuration. There you’ll have a better idea of the whole “under the hood” setup. Finding the right settings for your specific environment might take little time if you get knowledgeable on how the whole thing works.
Thank you,
Now I understand the engine structure better. I thought Weaver engine was only for print, and that the Merge engine created the PDFs.
It looks like my license limit the Weaver engine to 6, so I’ve changed to 6 now.
I cannot see any performance improvement though, but I am quite sure that just 1 Weaver engine can get stuck as you said, and slow everything down a lot.
I have a lot of small on demand jobs, which usually creates one 2-sided PDF. When I get say 1000 jobs at the same time, it can take a while for all of them to be generated, epecially if another process is printing larger print jobs at the same time.
How many jobs can PlanetPRess Connect Server run in parallel? Maybe worth looking into PRes Connect Server. Do you know the price different (approximately) or should I ask your local reseller?
Thta is definitely a reseller question
Guessed that 