Print file analysis limits

When parsing print jobs, the Print Processor creates a copy each print job's spool file. It then analyzes this spool file copy off to the side in order to prevent slowdown of the core print functionality on a server. In order to prevent full hard drives, Argos has built-in limits that can be adjusted. The Print Procesor has hardcoded limit of the 1Gb, at which point the spool files should not longer be created. Moreover, Argos contains two different parsing engines. One gathers detailed information, such as color content, but requires more CPU than the other, lightweight, parser that gathers less information. In order to preserve server performance, Argos switches between the two based on the spool file. The spool file size threshold for the two parsers is also adjustable.

To modify the limits, edit the Agent.Hosts.AgentService.exe.config file on the server you wish to adjust. A "0" (zero) value means "disabled."


This parameter controls the minimum free disk space. When reached, no spool files will be parsed.

<!-- 2Gb -->
<add name="MinFreeDiskSpace" value="2147483648"/>


This parameter controls maximum size of the spool file that will be parsed.

<!-- 500Mb -->
<add name="MaxSingleSpoolSize" value="524288000"/>


This parameter controls the threshold for using Advanced Parser. When reached, the faster parsers will be used for PCL, PS and EMF formats. In the lightweight parser (used for large spool files), color detection is available for EMF only.

<!-- 200Mb -->
<add name="FallBackSpoolSizeInBytes" value="209715200" />

When the MinFreeDiskSpace or MaxSingleSpoolFile conditions are exceeded, Argos reverts to the Job Ticket for its data. The Job Ticket is a preliminary set of statistics obtained from the Windows print spooler system. In many cases the Job Ticket data is accurate; in other cases it may not be as accurate as a fully parsed spool file.

Have more questions? Submit a request


Please sign in to leave a comment.