Pre-execution Memory Configuration via Decorated Code

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing computer execution systems lack a flexible and optimized memory allocation and management approach, often applying a single allocation scheme to all executable code, which can lead to inefficient memory usage and suboptimal performance across different applications and hardware configurations.

Innovation Solution

A configurable memory allocation and management system generates a configuration file with optimized settings that can be deployed prior to runtime, allowing for customized memory allocation and garbage collection parameters for individual applications and processes, using offline analysis and data collection from instrumented systems to determine valid configuration parameters based on static and dynamic state information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a single allocation scheme is applied to all executable code, then the system is simple to implement, but memory usage efficiency deteriorates

Engineering Contradiction:

Improvesimplicity of memory allocation systemVSAvoidmemory usage efficiency

Core Design Contradiction:

Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent segments memory allocation into multiple schemes (first allocation scheme for default cases, second allocation scheme for optimized cases) and assigns them to different executable code based on configuration files. This allows the system to maintain simplicity for most cases while achieving optimization for specific applications, resolving the contradiction between system simplicity and memory efficiency.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies different memory allocation characteristics to different portions of executable code by using configuration files to specify which code segments should use optimized allocation. This local differentiation enables efficient memory usage only where needed, while maintaining simple allocation elsewhere, thus resolving the contradiction between overall simplicity and localized efficiency.

Inventive Principle:

Principle #3Local quality

2Loss of energy

If optimized memory settings are applied to individual applications, then memory management efficiency is improved, but system complexity increases

Engineering Contradiction:

Improvememory management efficiencyVSAvoidsystem complexity

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

The patent performs memory allocation optimization in advance by using configuration files that are prepared before runtime. The configuration files contain pre-analyzed memory allocation boundaries and schemes, allowing the system to apply optimized settings without complex real-time analysis during execution. This preliminary preparation reduces runtime complexity while maintaining optimization benefits.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces configuration files as an intermediary between the application code and the memory allocation system. These files contain pre-computed optimization information that simplifies the runtime system's task, allowing optimized memory management without requiring complex integration between the application and memory management subsystems.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If configuration files with memory settings are deployed prior to runtime, then memory allocation efficiency is improved, but data privacy risks increase

Engineering Contradiction:

Improvememory allocation efficiencyVSAvoiddata privacy risks

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts sensitive operational data from production systems and moves it to separate configuration files that can be analyzed offline. This extraction allows the generation of optimized memory allocation schemes without exposing sensitive production data, reducing privacy risks while maintaining allocation efficiency.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses instrumented copies of applications to collect operational data and generate configuration files. These instrumented copies are separate from the production system, allowing data collection and analysis without compromising the privacy or security of the actual production data. The configuration files serve as copies of optimization parameters rather than containing sensitive data themselves.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS8656135B2Optimized memory configuration deployed prior to execution

Publication Date: 2014.02.18 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A configurable memory allocation and management system may generate a configuration file with memory settings that may be deployed prior to runtime. A compiler or other pre-execution system may detect a memory allocation boundary and decorate the code. During execution, the decorated code may be used to look up memory allocation and management settings from a database or to deploy optimized settings that may be embedded in the decorations.