Non-blocking Request Processing with Estimated Completion Timestamp
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In non-blocking request synchronization, the requestor and receiver face increased workload and power consumption due to frequent execution result retrieval attempts, as they cannot predict the execution completion timestamp of requests.
Innovation Solution
A non-blocking request processing method that determines an execution completion estimated timestamp and sends it to the requestor, allowing the requestor to wait for the estimated completion time before retrieving the execution result, thereby reducing unnecessary requests and power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the requestor sends multiple requests to retrieve execution result in non-blocking request synchronization, then the execution result can be retrieved, but the workload and power consumption of the requestor and receiver increase
Solution Approach 1:
The receiver performs preliminary action by calculating and providing the execution completion estimated timestamp to the requestor before the request is fully processed. This allows the requestor to know in advance when the execution will complete, so the requestor can wait for the estimated timestamp instead of continuously sending retrieval requests, thereby reducing power consumption while ensuring reliable execution result retrieval.
2Reliability
If the requestor sends multiple requests to retrieve execution result in non-blocking request synchronization, then the execution result can be retrieved, but the workload of the requestor and receiver increases
Solution Approach 1:
The receiver performs preliminary action by calculating and providing the execution completion estimated timestamp to the requestor before the request is fully processed. This allows the requestor to know in advance when the execution will complete, so the requestor can wait for the estimated timestamp instead of continuously sending retrieval requests, thereby reducing workload while ensuring reliable execution result retrieval.
3Loss of information
If the requestor continuously attempts to retrieve execution result without prediction, then the execution result can be obtained, but unnecessary requests and power consumption increase
Solution Approach 1:
The receiver provides feedback to the requestor in the form of an execution completion estimated timestamp, which allows the requestor to understand when the execution will complete. This feedback mechanism enables the requestor to wait for the estimated timestamp instead of continuously sending retrieval requests, thereby reducing unnecessary requests and power consumption while ensuring the execution result is eventually obtained.
Data Source
Figure 1A~1C
Figure 2
Figure 3A~3B
AI summary
A non-blocking request processing method and a device. The non-blocking request processing method includes: receiving a non-blocking request from a requestor (S31); determining an execution completion estimated timestamp of the non-blocking request (S32); and sending the execution completion estimated timestamp to the requestor (S33). By providing the execution completion estimated timestamp to the receiver, it may be avoided a case where the receiver cannot predict an execution completion timestamp of a request so as to attempt to retrieve an execution result for many times, which thus reduces workload and apparatus power consumption of the requestor and the receiver caused by frequent execution result retrieving request.