Optimized memory configuration deployed on executing code

• US 8,656,134 B2
• Filed: 11/08/2012
• Issued: 02/18/2014
• Est. Priority Date: 11/08/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Concurix Corporation
• Inventors: Gounares, Alexander G., Li, Ying, Garrett, Charles D., Noakes, Michael D.
• Primary Examiner(s): Bradley, Matthew
• Assistant Examiner(s): Bernard, Daniel
• Application Number:
  US13/671,836
• Publication Number:
  US 20130074092A1
• Time in Patent Office: 467 Days
• Field of Search: None
• US Class Current: 711/170
• CPC Class Codes: G06F 8/443 Optimisation
• CPC Class Codes: G06F 9/44557 Code layout in executable memory

Abstract

A configurable memory allocation and management system may generate a configuration file with memory settings that may be deployed at runtime. An execution environment may capture a memory allocation boundary, look up the boundary in a configuration file, and apply the settings when the settings are available. When the settings are not available, a default set of settings may be used. The execution environment may deploy the optimized settings without modifying the executing code.

Claims

1. A method performed by a computer processor, said method comprising:

receiving executable code;

executing said executable code;

during said executing, identifying a memory allocation boundary;

looking up said memory allocation boundary in a configuration database;

when said memory allocation boundary is present in said configuration database, determining a memory allocation scheme for said memory allocation boundary and applying said memory allocation scheme to said memory allocation boundary; and

when said memory allocation boundary is not present in said configuration database, applying a default memory allocation scheme to said memory allocation boundary.

2. The method of claim 1, said executable code being interpreted code.

3. The method of claim 1, said executable code being precompiled code.

4. The method of claim 1 further comprising:

receiving said configuration database from a remote device.

5. The method of claim 4, said configuration database being a configuration file.

6. The method of claim 1, said memory allocation boundary being a heap allocation event.

7. The method of claim 6, said heap allocation event being an initial heap allocation event.

8. The method of claim 6, said heap allocation event being a subsequent heap allocation event.

9. The method of claim 1, said memory allocation boundary being a process spawn event.

10. The method of claim 9, said configuration database being a hash table.

11. The method of claim 9, said process spawn event being one of a group composed of:

a function call;

an application launch;

a thread launch; and

a process launch.

12. The method of claim 9, said configuration database comprising process identifiers.

13. The method of claim 12, said process identifiers comprising a first process identifier comprising a first variable descriptor.

14. The method of claim 13, said first variable descriptor comprising a variable type descriptor.

15. The method of claim 13, said process identifiers comprising a calling process identifier.

16. A system comprising:

a processor;

an execution environment executing on said processor, said execution environment that;

receives executable code;

executes said executable code;

during said executing, identifies a memory allocation boundary;

looks up said memory allocation boundary in a configuration database;

when said memory allocation boundary is present in said configuration database, determines a memory allocation scheme for said memory allocation boundary and applies said memory allocation scheme to said memory allocation boundary; and

when said memory allocation boundary is not present in said configuration database, applies a default memory allocation scheme to said memory allocation boundary.

17. The system of claim 16, said execution environment comprising:

instrumentation to collect memory usage data while said executable code is executing, said memory usage data being used to generate said configuration database.

18. The system of claim 16 further comprising:

a configuration database manager that;

receives said configuration database.

19. The system of claim 18, said configuration database manager that further:

receives an update to said configuration database; and

updates said configuration database.

20. The system of claim 19, said configuration manager that further:

communicates with a remote server; and

receives said update from said remote server.