Request Prioritization in Client-Server Workload Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workload management in client-server infrastructures fails to prioritize requests based on their importance, leading to inefficient resource allocation and potential service level agreement breaches when servers reach capacity limits.
Innovation Solution
A method that sets request priorities based on request semantics, where synchronous requests are given high priority and asynchronous requests are excluded from the standard processing queue when server workload exceeds a threshold, with mechanisms for reprioritization and deferral based on request types and server capacity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all requests are handled by servers in the same way regardless of priority, then server processing is simple and uniform, but request prioritization based on importance is lost and service level agreements may be breached
Solution Approach 1:
The patent segments requests into different priority classes (high priority synchronous requests vs. low priority asynchronous requests) and applies different processing rules to each segment. High priority requests are included in the standard processing queue while low priority requests are excluded when server workload exceeds a threshold, enabling differentiated service treatment without uniform processing
Solution Approach 2:
The patent implements dynamic request queue management where the inclusion/exclusion of requests from the standard processing queue is determined by real-time server workload conditions. The system dynamically adjusts processing behavior based on current server capacity, transitioning between different processing modes as workload thresholds are crossed
2Speed
If synchronous requests are always processed with high priority, then critical data requests are responded to quickly, but server resources are consumed by less important requests during high workload periods
Solution Approach 1:
The patent applies different quality levels of service to different request types. High priority synchronous requests receive expedited processing with guaranteed inclusion in the standard queue, while low priority asynchronous requests receive best-effort processing and may be excluded during high workload periods, creating localized quality differentiation within the processing system
3Reliability
If the server excludes low priority requests from the processing queue during high workload, then server capacity is preserved for critical requests, but request processing time increases for excluded requests
Solution Approach 1:
The patent extracts low priority asynchronous requests from the standard processing queue when server workload exceeds the threshold, separating them from high priority synchronous requests. This extraction enables the server to focus resources on critical requests while maintaining a separate mechanism for handling extracted requests, reducing time loss for excluded requests through asynchronous processing
Data Source
AI summary
Work-load management in a client-server infrastructure includes setting request information in accordance with request semantics corresponding to a type of request from a client. The request semantics include different request-types provided with different priorities during processing. Within a server, requests with high priority are included in a standard request processing queue. Further, requests with low priority are excluded from the standard request processing queue when server workload of the server exceeds a predetermined first threshold value.