The conversion process in Foxit Rendition Server involves the instantiation of a conversion strategy that references an assembly line. The assembly line determines the required stations and their sequence for the conversion. This article aims to explain how the conversion process is instantiated and the mechanisms that allow for the reuse of conversion processes.
Instantiating the Conversion Process
1. For each conversion request, a strategy is provided, specifying the appropriate assembly line to be used.
2. Based on the selected assembly line, a conversion process is initiated by starting the RsAssemblyLineHost.exe.
3. It's important to note that instantiating a conversion process takes time. To optimize performance, conversion processes can be reused, particularly for smaller files.
Reuse of Conversion Processes
1. The reuse of conversion processes significantly accelerates the conversion time. The extent of reuse is determined by the configuration of the worker nodes.
2. By default, in the WorkerNodeConfig.base.xml file, the configuration is as follows:
<assemblyLine assemblyLineMaxUseCount="50" assemblyLineMaxIdleTime="600" assemblyLineMaxLifeTime="3600" assemblyLineCleanupTimerPeriod="5000">
3. Each conversion process can be reused up to 50 times (assemblyLineMaxUseCount) as long as it has not been idle for more than 10 minutes (assemblyLineMaxIdleTime) or has not exceeded one hour in age (assemblyLineMaxLifeTime).
4. When any of these criteria are reached first, the conversion process is terminated, and a new process is started upon the next incoming request.
5. It's important to note that reaching the assemblyLineMaxLifeTime does not terminate an ongoing conversion.
6. If a conversion is prematurely terminated due to an error, the currently used conversion process is also terminated.
7. Subsequent attempts to convert the same file should be slightly faster due to the reuse of the conversion process.
Multiple RsAssemblyLineHost.exe Instances
1. In certain scenarios, you may notice the presence of multiple instances of RsAssemblyLineHost.exe running.
2. This can occur when multiple conversion requests are being processed simultaneously or when there is a high demand for conversions.
3. The number of instances running simultaneously depends on the system resources and the configuration of Foxit Rendition Server.
By understanding how the conversion process is instantiated and the reuse of conversion processes, you can optimize the performance of Foxit Rendition Server for your conversion needs.
We hope this article provides you with a better understanding of how the conversion process is instantiated in Foxit Rendition Server. If you have any further questions or require additional assistance, please don't hesitate to reach out to our support team.