- Print
- PDF
Why Is my Lasernet Developer Processing Jobs Slowly?
While Lasernet can have very fast throughput, a number of factors can cause it to process slowly. This article will describe some checks that can be carried out which may be contributing to any delay in throughput.
First, check the size of the database that Lasernet generates. The default locations:
Lasernet 9: %ProgramData%\Formpipe Software\Lasernet 9\Service\InstanceName\Databases
Lasernet 8: %ProgramData%\Formpipe Software\Lasernet 8\InstanceName\Databases
If the database is larger than 0.5 GB, it is likely causing the slowdown.
Warning
The database can be removed. However, this will remove all jobs currently picked up by Lasernet.
Follow these steps to safely create more space in the database:
Stop all Lasernet input printers and input modules.
Stop the Lasernet Service when all jobs have finished processing. You can check if jobs are processing via Lasernet Monitor.
Move the .combiner, .databases, .failedjobs, and .pendingjobs folders from %ProgramData%\Formpipe Software\Lasernet 9\Service\InstanceName to a backup location.
Restart the Lasernet Service and wait for it to recreate the missing folders (.combiner, .databases, .failedjobs, and .pendingjobs).
Unpause all the inputs, and jobs should continue to process.
Further Checks
Check the build for any long delays caused by job combining or scheduling.
Check for any bottlenecks in the build (multiple inputs going through one form engine, for example). Formpipe can advise how to improve the build.
Check server resources are not close to 100% while Lasernet is processing slowly.