QMS 2060 Reference page 138

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 nonres-
ident emulations, it's possible that the emulations are having to reload
each time they're run. Adding to the emulation client may eliminate
the unloading and reloading of these emulations and, consequently,
increase throughput. QMS recommends that you should add at least
1 MB of physical RAM to your printer and increase this memory client
by 1 MB. If your printer has an optional hard disk and the disk swap-
ping option is turned on then you can increase the emulation memory
client using this memory.
» Note: You should add at least 1 MB to the emulation memory client
for each loadable emulation that your printer uses. Failure to add
memory to this client may prevent the printer from loading and using
the emulation. You should check the documentation accompanying
your loadable emulation for information on additional resource
requirements.
Also increase the emulation client if you're printing complex non-
PostScript jobs that may require more memory to process correctly.
Also known as K Mem Emul Tmp and Emulation Temporary, this cli-
ent sets the amount of system memory to be used by non-PostScript
emulations for storing downloaded fonts, forms, and macros. By dedi-
cating a portion of memory to this client, your printer can perform
"context switching," the ability to retain downloaded fonts and forms
even after the printer changes from one emulation to another. Context
switching prevents unnecessary repetitive downloading and traffic
congestion on networks.
Normally, this memory client doesn't need to be changed unless you
plan to download many different non-PostScript fonts.