Memory
PostScript Font Cache
Also known as K Mem PS Fonts and Font Cache, this memory client stores bitmapped representations of previously scaled PostScript fonts. This process reduces the number of times a font must be converted from outline form to bitmap form. Printing pages that have characters already stored in the font cache is immensely faster than printing characters not yet in the font cache.
As the font cache memory fills, the printer makes room for new bitmapped characters by erasing those that have been in the cache longest without being used. 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. You should be careful when increasing this client because the printer may spend more time searching the cache than it would scaling the character. This client has a limit to the maximum point size it will store.
Normally, you don’t 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’s 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:
n
n
You should experiment to see what font cache size works best for you.
PS Heap
Also known as K Mem PSHeap, Heap, PostScript VM, and Virtual Memory, this client holds downloaded fonts, PostScript operators, and forms.
Inefficiently coded PostScript jobs can consume an extremely large amount of virtual memory or leave objects in the PostScript heap after
QMS 4060 Print System Reference |