The Frame Buffer memory client holds rasterized or bitmapped
images of page faces which are ready to be sent to the print engine. A
frame holds the contents of each single page image. For example, a
600 dpi page printed on letter size paper would consume frame buffer
memory space as follows:
(600dpi x 600dpi x 8.5 in x 11 in) /8 = 4,207,500 bytes or 4.1 MB.
Because the frame buffer memory is so critical to the actual printing
of a page, its allocation takes precedence over that of other memory
clients. The number of frames needed to print at engine speed is
engine specific and depends on the size media and resolution. For
example, printing at 600x600 dpi requires four times the amount of
memory in the frame buffer than does 300x300 dpi.
If you are uncertain about how to configure your printer's memory,
use only the Administration/Memory/QuickConfig menu. This menu
appears if your printer does not have a hard disk attached or if the
disk swap option is disabled. Use this menu as a starting point before
trying manually to configure your printer's memory.
It provides a simple method of defining how much memory should go
to each of the clients for the most complicated printing conditions in
your environment. Menu options allow you to specify the largest
media size at the resolution you plan to use. Memory is then automat-
ically allocated to the clients.
Size is returned in Kilobytes.
Choices
02200-variable depending on options installed
Parsed from file QMS-MIB.mib
Module: QMS-MIB
Vendor: QMS, Inc.
Module: QMS-MIB
[Automatically extracted from oidview.com]
qmsClientFrameBuffer OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Frame Buffer memory client holds rasterized or bitmapped images of page faces which are ready to be sent to the print engine. A frame holds the contents of each single page image. For example, a 600 dpi page printed on letter size paper would consume frame buffer memory space as follows: (600dpi x 600dpi x 8.5 in x 11 in) /8 = 4,207,500 bytes or 4.1 MB. Because the frame buffer memory is so critical to the actual printing of a page, its allocation takes precedence over that of other memory clients. The number of frames needed to print at engine speed is engine specific and depends on the size media and resolution. For example, printing at 600x600 dpi requires four times the amount of memory in the frame buffer than does 300x300 dpi. If you are uncertain about how to configure your printer's memory, use only the Administration/Memory/QuickConfig menu. This menu appears if your printer does not have a hard disk attached or if the disk swap option is disabled. Use this menu as a starting point before trying manually to configure your printer's memory. It provides a simple method of defining how much memory should go to each of the clients for the most complicated printing conditions in your environment. Menu options allow you to specify the largest media size at the resolution you plan to use. Memory is then automat- ically allocated to the clients. Size is returned in Kilobytes. Choices 02200-variable depending on options installed" ::= { qmsMemory 9 }
| 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.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… |