Message flow control method, device and system

Abstract

The invention discloses a message flow control method, device and system, and belongs to the technical field of data processing. The method comprises the steps of judging whether a disk is currently in a busy state or not; judging whether message lag exists in a message set containing message data corresponding to the message request sent by the consumption end or not; and if the disk is currentlyin a busy state and the message set has message lag for the consumption end, returning message data acquired according to the message request to the consumption end according to preset delay time. According to the method, through detection of the state of the disk, when the disk is busy, flow limiting is carried out on the consumption end with message lag, the message pulling frequency of the consumption end with message lag is reduced by delaying message data returning, and therefore the frequency that the page cache is polluted is reduced.

Description

technical field [0001] The present invention relates to the technical field of data processing, in particular to a method, device and system for message flow control. Background technique [0002] Message middleware is a message transmission tool that focuses on sending and receiving data, and uses an efficient and reliable asynchronous message delivery mechanism to integrate various subsystems in a distributed system. Under normal circumstances, message middleware reads and writes data from page cache (page cache), which is more efficient than reading and writing data from disk. The software will not read and write data from the page cache (page cache), but instead read and write data from the disk, which leads to a sharp increase in disk read and write (disk I / O) utilization, which leads to the following three problems: [0003] 1. Since the data is read and written directly from the disk, the data read and written each time is transferred from the disk cache to the page ...

AI Technical Summary

Problems solved by technology

Under normal circumstances, message middleware reads and writes data from page cache (page cache), which is more efficient than reading and writing data from disk. The software will not read and write data from the page cache (page cache), but instead read and write data from the disk, which leads to a sharp increase in disk read and write (disk I / O) utilization, which leads to the following three problems:

[0003] 1. Since the data is read and written directly from the disk, the data read and written each time is transferred from the disk cache to the page cache, causing the page cache to be frequently polluted;

[0004] 2. Due to the frequent contamination of the page cache, the original page cache cannot be used normally by the consumer without message lag (lag), making it also read and write data from the disk , which reduces the number of transactions per second (TPS) read by the consumer (consumer);

[0005] 3. Due to the frequent pollution of the page cache, the writing of the message producer (producer) is blocked, and the delay becomes higher, which reduces the number of transactions per second (TPS) written by the message producer (producer)

Images