Memory management technique

• US 7,418,568 B2
• Filed: 01/05/2005
• Issued: 08/26/2008
• Est. Priority Date: 01/05/2005
• Status: Active Grant

• Current Assignee: Chant Sincere Co., Ltd., SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Maly, Gennady
• Primary Examiner(s): Bragdon; Reginald G.
• Assistant Examiner(s): CARDWELL, ERIC
• Application Number:
  US11/030,015
• Publication Number:
  US 20060149915A1
• Time in Patent Office: 1,329 Days
• Field of Search: 711/172
• US Class Current: 711/171
• CPC Class Codes: G06F 12/023 Free address space management

Abstract

Methods for allocating memory by a memory manager for an application are provided. The method may include the steps of allocating a first block size for a first amount of data, and allocating a second block size for memory allocated after the first amount of data. In some variations, the second block size is larger than the first block size. Subsequent block sizes may be also be allocated depending on the desired implementation and based on various threshold criteria. Related apparatuses, computer program products and computer systems are also provided.

Claims

1. A method comprising:

receiving a data allocation request from an application at a memory manager that controls allocation of a memory based on one or more factors pertaining to the memory;

allocating a first block size of the memory to one or more first blocks for a determined first amount of application data; and

allocating a second block size of the memory to one or more second blocks allocated after the first amount of application data, the second block size being smaller than the first block size if the memory manager determines that internal fragmentation of the memory is likely to occur based on the one or more factors and larger than the first block size if the memory manager determines that external fragmentation of the memory is likely to occur based on the one or more factors.

2. The method of claim 1, wherein the one or more factors comprises a number of objects saved in the memory manager.

3. The method of claim 1, wherein the one or more factors comprises a frequency of memory calls from the application.

4. The method of claim 1, wherein the one or more factors comprises an amount of the memory that is available.

5. The method of claim 1, wherein the one or more factors comprises an amount of the memory that has been consumed.

6. The method of claim 1, wherein the one or more factors comprises a flag set within the memory manager.

7. The method of claim 6, wherein the flag identifies the number of objects to be processed.

8. The method of claim 6, wherein the flag identifies an amount of memory to be consumed.

9. The method of claim 1, wherein the first block size is predetermined.

10. The method of claim 1, wherein the first and second block sizes are determined during run time.

11. The method of claim 1, further comprising allocating a third block size to one or more third blocks allocated after a second amount of data, wherein the third block size is larger than the second block size.

12. The method of claim 1, further comprising generating a memory manager having a flag, the flag defining when to change from the first block size to the second block size.

13. The method of claim 1, wherein the second block size is based on a factor chosen from the group comprising:

a number of objects saved, a frequency of memory calls from the application, an amount of available main memory, an amount of consumed main memory, and a flag set within a memory manager.

14. The method of claim 1, wherein the second block size is at least twice the first block size.

15. An apparatus comprising:

a processor that implements a memory manager coupled to an application and a memory having an assignment unit, the assignment unit configured to allocate one or more first blocks of the memory for a determined first amount of data and one or more second blocks of the memory after the first amount of data, the one or more first blocks having a first block size and the one or more second blocks having a second block size that is different than the first block size, the first and second block sizes being determined based on one or more factors pertaining to usage of the memory, the one or more factors comprising indications that internal or external fragmentation of the memory is likely.

16. The apparatus of claim 15, wherein the one or more factors is chosen from a group consisting of a number of objects, a frequency of memory calls from the application, an amount of available main memory, an amount of consumed main memory, and a flag set within a memory manager.

17. The apparatus of claim 15, wherein the second block size is larger than the first block size.

18. The apparatus of claim 15, wherein the assignment unit allocates one or more third blocks of the memory having a third block size after a second amount of data, the third block size being larger than the second block size.

19. A computer program product, tangibly embodied on a machine-readable storage device, that includes executable instructions for causing a computer system to:

receive a data allocation request from an application at a memory manager that controls allocation of a memory based on one or more factors pertaining to the memory;

allocate a first block size of the memory to one or more first blocks for a determined first amount of application data; and

allocate a second block size of the memory to one or more second blocks allocated after the first amount of application data, the second block size being smaller than the first block size if the memory manager determines that internal fragmentation of the memory is likely to occur based on the one or more factors and larger than the first block size if the memory manager determines that external fragmentation of the memory is likely to occur based on the one or more factors.

20. A method comprising:

receiving an allocation request from an application at a memory manager module that manages allocation of a memory;

determining, within the memory manger, whether internal or external fragmentation of the memory is likely to occur based on an observed pattern of memory usage; and

allocating one or more blocks of the memory for the application, the one or more blocks having a first block size if internal fragmentation is determined to be likely and a second block size if external fragmentation is determined to be likely, the second block size being larger than the first block size.

21. A method as in claim 20, wherein the determining whether internal or external fragmentation of the memory is likely to occur comprises analyzing one or more of an amount of the memory consumed by the application, an amount of the memory that is available for use, a number of objects processed by the application, and a frequency of memory calls by the application.