Multi-threaded event processing component

Abstract

The invention discloses a multi-thread event processing component, which realizes unified management of events by unifying external event definition basic types, packaging high-concurrency lockless queues, unifying semaphore and IO multiplexing wake-up mechanisms, and realizes low-delay and high-concurrency access of thread communication while reducing development difficulty and cost. According tothe technical scheme, through a unified event model, underlying event management and thread notification management mechanisms are decoupled, the cost of application developers for multi-thread eventdevelopment is reduced, and the event processing capacity of applications is improved. Compared with an existing event processing method, on one hand, the consistency problem of underlying network communication and internal event communication is solved; by means of the embedded memory pool model, the lock-free queue and other mechanisms, the event processing efficiency of the application programis greatly improved, the complexity of the system is lowered, and meanwhile high concurrency and low delay are guaranteed.

Description

technical field [0001] The invention relates to financial software technology, in particular to a low-delay, high-concurrency multi-thread parallel event processing component applied in the field of financial futures. Background technique [0002] In the financial futures market, there is an urgent need for low-latency, high-concurrency multi-threaded parallel processing. On the one hand, it must meet the low-latency requirements in extremely fast trading scenarios; Require. In terms of the usage characteristics of CPU and IO, there are two common application scenarios: one is CPU-intensive, which mainly occurs in scenarios with a large amount of calculation. In this scenario, threads generally use the semaphore mechanism to Trigger the delivery of messages; one is IO-intensive, which is mainly for common application scenarios such as network data reading and writing, disk IO data reading and writing, etc. In this scenario, the wake-up of threads is mainly triggered through...

AI Technical Summary

Problems solved by technology

[0003] The current common solutions, such as the libevent open source library, realize the unified and simple abstraction of events, and solve the event management under the condition of IO multiplexing. For IO-intensive applications, the complexity of the code is reduced to a certain extent. , but for application developers, there are two shortcomings: one is that the interface package is too simple, the development and maintenance costs are high, and the other is that it fails to meet the CPU-intensive development requirements

Images