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 con-
verted 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 bit-
mapped characters by erasing those that have been in the cache
longest without being used. Increasing the memory allocated to this
client, allows the printer to 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 recom-
mended font cache size is in the following ranges:
* 128-256 KB for 300x300 dpi printing
* 256-512 KB for 600x600 dpi printing
* 384-512 KB for 1200x1200 dpi printing
You should experiment to see what font cache size works best for
you.
Size is returned in Kilobytes.
Parsed from file QMS-MIB.mib
Module: QMS-MIB
Vendor: QMS, Inc.
Module: QMS-MIB
[Automatically extracted from oidview.com]
qmsClientFontCache OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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 con- verted 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 bit- mapped characters by erasing those that have been in the cache longest without being used. Increasing the memory allocated to this client, allows the printer to 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 recom- mended font cache size is in the following ranges: * 128-256 KB for 300x300 dpi printing * 256-512 KB for 600x600 dpi printing * 384-512 KB for 1200x1200 dpi printing You should experiment to see what font cache size works best for you. Size is returned in Kilobytes." ::= { qmsMemory 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.480.1.5.1 | qmsMEMPhysical | 0 | 0 | Size of the physical memory in MB. |
| 1.3.6.1.4.1.480.1.5.2 | qmsMEMTotal | 0 | 0 | Size of the total virtual memory in MB. Note: If no hard disk is installed, this will be the size of physical memory. |
| 1.3.6.1.4.1.480.1.5.3 | qmsClientSystem | 0 | 0 | Also known as System Use, this non-configurable client is the amount of RAM used to run the printer's operating system. It's nev… |
| 1.3.6.1.4.1.480.1.5.4 | qmsClientSpool | 0 | 0 | Also known as Host Input and K Mem for Spool, this memory client stores incoming data from all the interfaces until the emulatio… |
| 1.3.6.1.4.1.480.1.5.5 | qmsClientEmulation | 0 | 0 | Also known as K Mem Emulation, this client is used to store any optional or loadable emulations, such as LN03 Plus or QUIC II. In… |
| 1.3.6.1.4.1.480.1.5.6 | qmsClientHeap | 0 | 0 | Also known as K Mem PSHeap, Heap, PostScript VM, and Virtual Memory, this client holds downloaded fonts, PostScript operators, a… |
| 1.3.6.1.4.1.480.1.5.8 | qmsClientDisplayList | 0 | 0 | Also known as K Mem Display, this client stores compressed repre- sentations, or blocks, of the pages to be printed. It takes ap… |
| 1.3.6.1.4.1.480.1.5.9 | qmsClientFrameBuffer | 0 | 0 | The Frame Buffer memory client holds rasterized or bitmapped images of page faces which are ready to be sent to the print engine… |
| 1.3.6.1.4.1.480.1.5.10 | qmsClientEmulTemp | 0 | 0 | Also known as K Mem Emul Tmp and Emulation Temporary, this cli- ent sets the amount of system memory to be used by non-PostScrip… |
| 1.3.6.1.4.1.480.1.5.11 | qmsClientDisk | 0 | 0 | This memory client stores frequently used data in system memory instead of continually storing and retrieving it from a hard dis… |
| 1.3.6.1.4.1.480.1.5.13 | qmsClientColorMatching | 0 | 0 | The Color Matching memory client provides storage space for the control and operation of the Color Matching feature. The availa… |
| 1.3.6.1.4.1.480.1.5.14 | qmsClientHPStoragePool | 0 | 0 | Also known as K Mem HP Pool, HP Heap, HP VM, and Virtual Memory, this client holds downloaded fonts, and forms. Inefficiently cod… |