Dynamic Load Testing Coordinator Thread Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional load testing frameworks lack external control over concurrency increase during testing, leading to prolonged performance testing durations and inefficient load analysis.
Innovation Solution
A system and method for dynamic load testing that includes a coordinator thread and waiting threads, allowing external control to increment concurrency dynamically within a running load-testing environment, enabling threads to unlock and access the target application as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If load testing framework pre-determines maximum load and executes test without external control, then test execution can proceed automatically, but overall duration of performance testing increases considerably
Solution Approach 1:
The patent implements dynamic control of concurrency levels during load testing by allowing external intervention to modify the number of active threads. The load testing framework transitions from a static, pre-determined load configuration to a dynamic system where concurrency can be adjusted in real-time based on testing requirements, thereby reducing overall test duration while maintaining automation.
Solution Approach 2:
The patent introduces a feedback mechanism that enables external monitoring and control of the load testing process. The system provides feedback about current concurrency levels and test progress, allowing external systems to make informed decisions about when to increase or decrease load, optimizing the overall testing duration.
2Device complexity
If load testing framework does not provide external control over concurrency increase, then framework structure remains simple, but end users cannot dynamically change load for testing
Solution Approach 1:
The patent segments the thread management functionality into distinct components: a thread pool manager that handles thread creation and destruction, and a concurrency controller that manages the number of active threads. This segmentation allows the framework to maintain a relatively simple core structure while adding dynamic control capabilities through modular components.
Solution Approach 2:
The patent introduces an intermediary layer between the load testing framework and the target application - a concurrency controller that acts as a mediator. This intermediary manages the complexity of dynamic concurrency control by providing a simplified interface for external systems to adjust load levels without directly modifying the framework's internal structure.
3Productivity
If concurrency level is increased during test execution, then load testing coverage improves, but system stability may be compromised due to uncontrolled load bursts
Solution Approach 1:
The patent implements periodic control of concurrency levels rather than continuous uncontrolled increase. The system can periodically adjust the number of active threads based on predefined patterns or monitoring data, allowing load testing coverage to be expanded in a controlled manner that maintains system stability through rhythmic rather than explosive load application.
Solution Approach 2:
The patent enables controlled parameter changes in the concurrency level during test execution. Instead of fixed pre-determined load levels, the system allows dynamic adjustment of the number of active threads as a controllable parameter, enabling optimization of both testing coverage and system stability through monitored parameter modification.
Data Source
AI summary
A system and method for dynamic load testing on a target application are provided. The method includes, receiving a request for varying load on a target application in running load-testing environment. The running load-testing environment has a plurality of threads being executed for load-testing. The plurality of threads has a coordinator thread and one or more waiting threads. Further, the one or more waiting threads are locked from accessing the target application and the coordinator thread capable of unlocking the one or more waiting threads. The coordinator thread is executed based on the request to unlock the one or more waiting threads. The unlocked threads access the target application to test the load.