QMS 2025, Administrator'S Manual

Page: 117 / 158

Memory Clients
7-11 Memory Submenu
As the font cache memory fills, the printer erases bitmapped charac-
ters that have been in the cache longer than the others without being
used to make room for new characters. By increasing the memory
allocated to this client, the printer can store more characters and
spend less time erasing and replacing characters in the cache.
Normally, you do not need to change this memory client unless you
use a large number of fonts at various point sizes. If you do, you may
allocate additional memory to this client to improve printer perfor-
mance. There is no specific formula to use in figuring the amount of
memory required by the font cache, but after a certain point, large
font caches cause the printer to take longer to print than smaller font
caches because of the search time through the cache.
The recommended font cache size is in the following ranges:
■
128 KB to 256 KB for 300 dpi printing
■
200 KB to 400 KB for 400 dpi printing (3225/2025 Print Systems)
■
200 KB to 400 KB for 600 dpi printing (3825 Print System)
You should experiment to see what font cache size works best for
you. The system will not allow you to set this memory client too low.
The maximum setting is 99999 and is related to the total amount of
memory and the amount of memory configured to the other clients.
The default is 256 KB.
Emulation
Also known as K Mem Emulation, this client is used to store any avail-
able emulations, such as CCITT, LN03 Plus, HP PCL, HP-GL, and
imPRESS. Increasing this client’s memory allows more complicated
non-PostScript jobs to print and allows larger emulations or multiple
emulations to be loaded and ready to process jobs.
If an emulation is loaded to process a print job and there is not
enough memory in the emulation client, another emulation already
loaded may be unloaded automatically to obtain enough memory. If
you notice a delay in printing between jobs that have different non-
resident emulations, it is possible that the emulations are having to
reload each time they are run. Adding to the emulation client may