Abstract: An off-screen buffer manager controls when the off-screen buffer is destroyed and re-created improving system performance. A screen request is received for a Java screen component and a determination is made whether there is already an off-screen buffer. If there is not an off-screen buffer, a new off-screen buffer is created and the component requesting the screen request is associated with the off-screen buffer. If an off-screen buffer already exists, a determination is made as to whether the off-screen buffer is large enough to handle the incoming request. If the off-screen buffer is large enough to handle the request, the existing off-screen buffer is used to handle the request, otherwise, the existing off-screen buffer is deleted and a new off-screen buffer is created and the component identifier of the deleted off-screen buffer is associated with the new off-screen buffer.

Abstract: An off-screen buffer manager controls when the off-screen buffer is destroyed and re-created improving system performance. A screen request is received for a Java screen component and a determination is made whether there is already an off-screen buffer. If there is not an off-screen buffer, a new off-screen buffer is created and the component requesting the screen request is associated with the off-screen buffer. If an off-screen buffer already exists, a determination is made as to whether the off-screen buffer is large enough to handle the incoming request. If the off-screen buffer is large enough to handle the request, the existing off-screen buffer is used to handle the request, otherwise, the existing off-screen buffer is deleted and a new off-screen buffer is created and the component identifier of the deleted off-screen buffer is associated with the new off-screen buffer.

Abstract: A graphical system resource monitor is provided to depict, in real-time, a data processing system's internal resource utilization. A window or viewport of a data processing system displays user specified internal system resources, such as memory, CPU, or peripheral device availability/utilization. This graphical representation of the `state` of the data processing system's resources is maintained in real-time, while the impact on the system's performance in providing such information is kept to a minimum. This is accomplished through a combination of various techniques, including specialized device drivers for the respective devices coupled with a unique data reduction technique. The graphical results of these resource monitors are continually updated in real-time. This real-time support provides an immediate and accurate representation of the internal operations of the data processing system. Further, these resources can be monitored at the process level of a multiprocessing system.

Abstract: A graphical system resource monitor is provided to depict, in real-time, a data processing system's internal resource utilization. A window or viewport of a data processing system displays user specified internal system resources, such as memory, CPU, or peripheral device availability/utilization. This graphical representation of the `state` of the data processing system's resources is maintained in real-time, while the impact on the system's performance in providing such information is kept to a minimum. This is accomplished through a combination of various techniques, including specialized device drivers for the respective devices coupled with a unique data reduction technique. The graphical results of these resource monitors are continually updated in real-time. This real-time support provides an immediate and accurate representation of the internal operations of the data processing system. Further, these resources can monitored at the process level of a multiprocessing system.

Abstract: A system and apparatus is described to check pages in memory that are allocated to all processes and the operating system, and to check the pages in memory that are allocated to each individual process, in order to determine total RAM usage and RAM usage for a particular process, respectively. In order to determine total RAM usage for all processes and the operating system, a page frame table is used to count all memory pages being used. System memory pages, all process pages and unassigned pages are marked in a page frame table using a specific marking process. These marked pages are then summed and categorized for their particular usage, i.e. free memory, system memory or process memory. The RAM memory usage for a particular process can also be determined. First, RAM usage from operating system control blocks assigned to the specific process is computed.