Recently to do a project, demand is the underlying equipment with sockets to send data, receive on my side, data for hexadecimal number (a receiving more than 16000), and then the back-end processing, warehousing, through echarts, according to the request of a second refresh, now is through ajax brushes regularly, 1 seconds will have a problem? Or, to put the websocket implementation is better, how to implement, or there is a better way, for bosses to solve.

CodePudding user response:

If you say you have a problem is data response time is too long cause page caton, I did think of a more can't be very smart solutions, to create a new table, the ajax request and receiving socket data time stagger, do an ajax request data is always had already exists in the list, the received data of the socket is always after the ajax request, so it can guarantee the ajax is just a lookup table, page won't caton, but there will be a delay, delay depends on the size of the you set the maximum number of data table, don't know if you can understand