Node-based event processing method and related server device

Abstract

The invention relates to a node-based event processing method and a related server device. When an event processing thread encounters an intensive computing event, an auxiliary processor is called, and the intensive computing event is carried out by the auxiliary processor, so a master processor in which the event processing thread is located can continuously read and process a next to-be-processed event, the event processing thread is prevented from being occupied for a long time by massive computing operations related to the intensive computing event, the processing efficiency of the event processing thread for the intensive computing event can be improved, a congestion phenomenon is avoided, and the performance of the related device or system is improved.

Description

technical field [0001] The present disclosure relates to the technical field of event processing, in particular to a Node-based event processing method and related server equipment. Background technique [0002] Node is a Javascript script running platform based on the Google V8 engine. It is applied to the server side and used to conveniently build fast-response and easy-to-extend network applications. One of the main features of Node is to use single-threaded processing, that is, there is only one event processing thread in Node at the same time, and all Javascript codes are executed by this event processing thread, which can avoid the problem of multi-threaded programming that needs to pay attention to state synchronization at all times, and avoid code A deadlock phenomenon occurs during the running process, and the performance overhead caused by thread switching is eliminated at the same time. [0003] However, the introduction of a single-threaded processing method als...

AI Technical Summary

Problems solved by technology

[0004] like figure 1 In the signal flow diagram shown, the Node-based event processing thread (running in the Central Processing Unit (CPU)) processes the intensive computing event corresponding to request 2, although it receives the request 1 returned by the I / O device successively The corresponding target data and the request 3 sent by the client cannot be processed, so they can only be stored in the event queue. The returned data is forwarded to the client, and the I / O device is notified to return the target data corresponding to request 3 through an asynchronous call, which seriously affects the response speed of the server to the client.

[0005] It can be seen that when the existing Node-based event processing method encounters intensive computing events, the processor resources are occupied for a long time, which makes the system in a blocked state and the overall system performance declines.

Images