Electrical computers and digital processing systems: memory – Storage accessing and control – Control technique
Reexamination Certificate
1996-06-17
2001-10-02
Banankhah, Majid A. (Department: 2151)
Electrical computers and digital processing systems: memory
Storage accessing and control
Control technique
C711S151000, C711S158000, C709S241000
Reexamination Certificate
active
06298422
ABSTRACT:
The invention relates to a method for improving the efficiency of multitasking application programs in a micro-computer system. More particularly, the invention relates to a method for reducing the memory and CPU resources allocated to, running, inactive application programs.
BACKGROUND OF THE INVENTION
A principal advantage of a WINDOWS based operating system is its capability to enable a plurality of application programs to multitask or run simultaneously. However, only one of these programs owns the input focus at a time. The user determines which application has the input focus (the “active application”), and receives the user's keystrokes and mouse clicks. Applications which are running but do not have the input focus, are termed “inactive”. Inactive applications are often “minimized” by a user, which action causes any visible windows belonging to the application to be hidden and the application to represented by a small picture (icon) or text representation, typically located in the bottom portion of the display, indicating that the application is running, but is not active. Frequently, a single active application is used by the user for an extended period of time, and the user does not switch to other running, inactive applications very often.
Applications that are running, but inactive continue to receive processor time and often continue to consume substantial quantities of system memory, including memory occupied by program code and data. Therefore, the existence of one or more running, inactive applications increases the load on the system resources (e.g., memory consumption and CPU usage), thus hampering the overall performance of the computer system.
An application may readily detect when it has been made inactive, and it has the ability to reduce its contribution to overall system load in a number of ways, including: causing at least a portion of its memory to be discarded or deallocated; marking its pageable data segments as candidates to be paged out by the virtual memory manager; releasing desktop or display resources that are not necessary while it is inactive; and reducing its processor usage by disabling timers, ceasing background execution, etc. However, application programs often do not take any of these steps to reduce consumption of system resources. One reason for this is that releasing system resources may increase the time needed to reactivate the application. Additionally, the steps that may be taken to reduce an application's system load are dependent on the programmers who designed the application, are therefore specific to that application, and do not usually apply to other application programs that may be contributing to the system load. Furthermore, the effort expended on reducing overhead may be wasted if the user intends to re-activate the application almost immediately.
An application's 16 or 32 bit program code and resource segments consume a significant portion of the system resources utilized by the application. Many such segments are provided with an attribute specifying that the segment is “discardable”, in its entirety, at the discretion of the WINDOWS Kernel or at the request of the application program. When a segment is discarded, the memory that has been allocated to the segment is released to the operating system as free memory. Such segments contain readonly program code or resources, so the Kernel is able to reload or reconstitute the segment from its disk image contained in the programs's executable file, when it is needed. For 16 bit programs, these discardable segments are allocated from the WINDOWS Global Heap memory. For Win32 programs (32 bit programs), discardable segments are assigned to linear memory backed by a memory file mapping. The memory associated with these discardable segments in Win32 programs is available to be released by the WINDOWS memory manager to reduce overall consumption of system memory resources.
As for 16 bit programs, the Kernel only resorts to discarding when available linear memory is exhausted, which is an infrequent occurrence, because linear memory is generally abundant. Moreover, the Kernel discards discardable segments indiscriminately, whereby segments belonging to the active application are as likely to be discarded as those belonging to inactive applications. Additionally, because free physical memory is typically exhausted long before this compaction occurs, some portions of the application, including its discardable data, are likely to have been paged out to the virtual memory swap file. Because substantial portions of inactive applications may be accessed on a regular or frequent basis due to message handling of system messages and broadcasts, these portions are not likely to be paged out. Note that this is also applicable for 32 bit applications.
One prior art attempt to conserve system resources utilized by inactive programs is the program known as WinProbe, which is commercially available from QUARTERDECK. WinProbe is a system monitor program that presents to the user the status of various components of the operating system. Additionally, it provides a “memory optimizer”, which causes the WINDOWS Global Heap to be “optimized” on an immediate basis, or at a settable interval for as long as WinProbe remains loaded. In order to optimize the heap, WinProbe issues a GlobalCompact call to the Kernel causing all discardable segments in the Global Heap to be discarded. But this approach has the drawback of requiring the user to execute a separate program in order to perform the compaction operation. It has a further drawback of causing all loaded segments to be discarded indiscriminately. Additionally, a percentage of these segments will have to be reloaded by the Kernel immediately as they are accessed by running programs. Yet a further drawback is that WinProbe has no effect on memory containing data or memory assigned to 32 bit processes.
Therefore, it is an object of the invention to conserve system resources consumed by running, inactive programs, while overcoming the drawbacks of prior art methods of doing so.
SUMMARY OF THE INVENTION
In accordance with the present invention, the efficiency and operating ability of multitasking application programs in the WINDOWS is improved by reducing the memory and CPU resources consumed by running, inactive application programs. The method of the invention, which is preferably user activated, suspends an application program by discarding and/or compressing the memory occupied by an application at the time it is minimized, or at the direction of the user, preferably by selection of a button in the title bar of the application or some other similar program object.
In a preferred embodiment, the method for reducing the memory requirements and CPU cycle consumption of an executing program in a suspended state suspends the program by intercepting the entry points of the program. The contents of the memory occupied by the program and its data objects are then compressed, wherein the compressed data is stored at another region in the memory. The memory region containing the original, uncompressed data is then designated as free memory.
REFERENCES:
patent: 5371871 (1994-12-01), Spilo
patent: 5533175 (1996-07-01), Lung et al.
patent: 5559978 (1996-09-01), Spilo
patent: 5664095 (1997-09-01), Cox et al.
patent: 5699539 (1997-12-01), Garber et al.
patent: 5765157 (1998-06-01), Lindholm et al.
Jeffrey M. Richter, “Windows 3.1: A Developer's Guide”, M&T Books, pp. 16, 19, 34, 65, 67, 373, 698, 1992.*
James L. Conger, “Windows API Bible”, The Waite Group, Inc., pp. 30-31, 892-894, 1992.
Daub Jonathan A.
Spilo Michael L.
Banankhah Majid A.
Darby & Darby
Network Associates, Inc.
LandOfFree
Method for reducing the memory requirements for an... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method for reducing the memory requirements for an..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method for reducing the memory requirements for an... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2602405