Application Environment Modeling for Software Performance Benchmarking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software application environments often fail to meet desired performance criteria due to suboptimal technology product combinations, leading to inefficiencies and the need for frequent redesigns in response to changing user traffic and technological advancements.

Innovation Solution

An application manager system that tests and recommends alternative technology product combinations for software applications, simulating performance in different environments to identify optimal configurations and adapt to evolving requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If an application environment is designed based on desired performance criteria using a set of technology products, then the application can be deployed, but the application may not perform in a desired manner when actually deployed due to unforeseen traffic volumes or changing requirements

Engineering Contradiction:
Improveapplication performanceVSAvoidadaptability to changing traffic and requirements
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary testing of multiple technology product combinations in simulated environments before actual deployment. By pre-evaluating different configurations against various performance criteria and traffic scenarios, the system identifies optimal combinations that are likely to perform reliably under expected conditions while providing a foundation for future adaptation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system varies multiple parameters including different technology products, their configurations, and combinations to create diverse application environment models. By systematically changing these parameters and evaluating performance across different scenarios, the system identifies optimal configurations that balance current performance requirements with future adaptability.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If the application environment is redesigned to accommodate changed application requirements or traffic volumes, then the application can handle new demands, but the technology landscape continuously changing requires frequent redesigns

Engineering Contradiction:
Improveability to handle changed requirementsVSAvoidtime for redesign
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-tests multiple technology combinations and evaluates their performance characteristics before deployment. By having pre-established performance data and validated configurations, the system can quickly adapt to changing requirements without time-consuming redesigns, as the foundation of tested configurations is already in place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates dynamic application environment models that can be adjusted based on changing requirements. Rather than static fixed configurations, the system maintains flexible models that can be reconfigured by selecting different technology products and combinations from pre-evaluated options, enabling rapid adaptation to new demands.

Inventive Principle:
Principle #15Dynamics

3Productivity

If multiple technology products are tested and evaluated to find the optimal combination, then the application performance can be optimized, but the complexity of testing and evaluation increases

Engineering Contradiction:
Improveapplication performance optimizationVSAvoidtesting and evaluation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing and evaluation process is segmented into distinct phases: creating application environment models, selecting technology products, configuring combinations, running tests, and analyzing performance. By breaking down the complex evaluation process into manageable segments, the system can systematically explore multiple combinations without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates simulated environment copies that replicate production conditions without the full complexity of actual deployment. By testing technology combinations in these simplified but representative simulated environments, the system can evaluate performance characteristics efficiently before actual deployment, reducing the complexity of comprehensive testing.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If the application environment is designed for a specific number of users, then the server can be sized appropriately, but unexpected traffic volumes may exceed the server's capability

Engineering Contradiction:
Improveserver sizingVSAvoidserver capability under load
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system evaluates multiple technology product combinations and their performance characteristics across different traffic scenarios. By analyzing how different configurations perform under varying load conditions, the system can select combinations that provide appropriate server sizing for expected traffic while maintaining reliability under unexpected demand through configuration flexibility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12517804B2Generating technology environments for a software application
Publication Date: 2026.01.06 BANK OF AMERICA CORP
  • US12517804B2 patent drawing
  • US12517804B2 patent drawing
  • US12517804B2 patent drawing

AI summary

A system is configured to obtain information relating to a current application environment of a software application including information relating to technology components and technology products being used in the current application environment. The system builds one or more model application environments for the software application. The system receives a request for a level of performance associated with a technology component and selects a technology product for the technology component that satisfies the requested level of performance, based on a performance benchmark of the technology product. The system builds one of the model application environments using the selected technology product for the technology component that satisfies the requested level of performance.