You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In device-modbus-go, I added an intermediate layer device service service to parse device parameters and other functions. After parsing, it calls the restful interface in the command service of device-modbus-go. Activating automatic collection for fifty devices would lead to high CPU usage for these two services (each read operation on device resources must go through intermediate layer parsing and forwarding). I wonder if frequent creation of connections for HTTP requests consumes resources, but changing it to messaging's command using message bus mechanism still shows no significant improvement. What optimization suggestions do you have for this situation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In device-modbus-go, I added an intermediate layer device service service to parse device parameters and other functions. After parsing, it calls the restful interface in the command service of device-modbus-go. Activating automatic collection for fifty devices would lead to high CPU usage for these two services (each read operation on device resources must go through intermediate layer parsing and forwarding). I wonder if frequent creation of connections for HTTP requests consumes resources, but changing it to messaging's command using message bus mechanism still shows no significant improvement. What optimization suggestions do you have for this situation?
Beta Was this translation helpful? Give feedback.
All reactions