Method for processing multiprogress message and method for processing multiprogress talk ticket

Abstract

This invention relates to a multi-process information process method and a multi-process ticket process method, in which the ticket process method used in parallel process to tickets in the charge system includes 1, setting up a shared memory for every process, 2, the process fetches the tickets for processing in the shared memory block, 3, distributing the tickets and storing them in the shared memory according to the preset load balance rule based on the current occupation situation of the memory block and storing the tickets with the same charged numbers in a same shared memory.

Description

technical field [0001] The invention relates to a multi-process message processing method, in particular to a load balancing method for multi-process message processing. The invention also relates to a real-time billing method, in particular to a multi-process bill processing method. Background technique [0002] The existing multi-process message processing method is to distribute data to the components for processing through the agreed inter-process communication (IPC) mechanism (such as pipes, sockets, message queues) or directory files among the components. [0003] .Taking sockets (pipelines) as an example, a connection is established between the pre-processing process and the subsequent processing process (in the pipeline mechanism, one reads and one writes two pipelines), one process writes data, and the other The process reads data from it; the process of the subsequent processing link periodically feeds back the processing speed to the process of the pre-processing...

AI Technical Summary

Problems solved by technology

However, the application program interface (API) of the message queue is limited, and the subsequent processing process cannot know the backlog of data in the queue; in addition, this mechanism has limited performance and cannot adapt to a large amount of data exchange

[0007] To sum up, with the existing technology, the stagnation of tasks in the subsequent processing link will cause the waiting of the pre-processing link, and then the pre-processing link cannot schedule other tasks, which will cause some processes to be busy while other processes are in a waiting state. Load imbalance between processes

Although the existing message queue mechanism has a buffering effect, the inter-process communication (IPC) does not provide an application program interface (API) to access the state of the queue

Moreover, in the prior art, if the process is abnormal, the operating system will reclaim the memory used by the process, resulting in the loss of data in the block of memory

The performance of the mechanism adopted by the existing technology is relatively slow, which cannot meet the needs of real-time business

Images