This memory client stores frequently used data in system memory
instead of continually storing and retrieving it from a hard disk. If a
hard disk is used and a lot of disk access is required, adding memory
to the disk cache may increase the printer's performance.
For example, if many fonts are stored on disk, faster access to these
fonts is achieved by increasing the disk cache size. Conversely, if no
hard disk is used, the disk cache will automatically be set to 0 KB until
a hard disk is installed and formatted. However, when one or more
hard disks are installed and formatted, disk cache is automatically
allocated 256 KB.
The disk cache is a high-speed temporary buffer for data going to and
from the hard disk. It can speed up the printer in two ways:
* Information such as frequently referenced fonts and logos may
still be in the cache and may not have to be pulled off a hard disk
each time they're needed.
* Information being written to a hard disk can be held in the cache
temporarily until a more convenient time to be written to disk.
The amount of memory needed for the disk cache client is dependent
on the size of the disk, the number of disks, the number of subdirecto-
ries on each disk, and the amount of memory dedicated to caching.
As long as the disk cache is enabled and there is enough memory in
the disk cache, all disks are accessible. If insufficient memory is allo-
cated to the disk cache, some disks may be seen while others are
not.
The recommended amount of memory for the disk cache client for all
hard disk is as follows:
* 45 KB internal usage
* 0.5 KB per MB of disk storage total for all disks
* 100 KB of memory dedicated to caching
For example, the recommended amount of memory for the disk cache
for a single 120 MB hard disk would be 208 KB, and for two 120 MB
hard disks it would be 268 KB.
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]
qmsClientDisk OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This memory client stores frequently used data in system memory instead of continually storing and retrieving it from a hard disk. If a hard disk is used and a lot of disk access is required, adding memory to the disk cache may increase the printer's performance. For example, if many fonts are stored on disk, faster access to these fonts is achieved by increasing the disk cache size. Conversely, if no hard disk is used, the disk cache will automatically be set to 0 KB until a hard disk is installed and formatted. However, when one or more hard disks are installed and formatted, disk cache is automatically allocated 256 KB. The disk cache is a high-speed temporary buffer for data going to and from the hard disk. It can speed up the printer in two ways: * Information such as frequently referenced fonts and logos may still be in the cache and may not have to be pulled off a hard disk each time they're needed. * Information being written to a hard disk can be held in the cache temporarily until a more convenient time to be written to disk. The amount of memory needed for the disk cache client is dependent on the size of the disk, the number of disks, the number of subdirecto- ries on each disk, and the amount of memory dedicated to caching. As long as the disk cache is enabled and there is enough memory in the disk cache, all disks are accessible. If insufficient memory is allo- cated to the disk cache, some disks may be seen while others are not. The recommended amount of memory for the disk cache client for all hard disk is as follows: * 45 KB internal usage * 0.5 KB per MB of disk storage total for all disks * 100 KB of memory dedicated to caching For example, the recommended amount of memory for the disk cache for a single 120 MB hard disk would be 208 KB, and for two 120 MB hard disks it would be 268 KB. Size is returned in Kilobytes." ::= { qmsMemory 11 }
| 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.7 | qmsClientFontCache | 0 | 0 | Also known as K Mem PS Fonts and Font Cache, this memory client stores bitmapped representations of previously scaled PostScript… |
| 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.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… |