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
Current polling and timeout mechanism has problems in performance perspective.
SERVAL server keeps handling particular agent connection permanently.
Therefor SERVAL server needs a lot of thread for processing agents.
Huge number of threads need huge memory resources on Linux.
In order to use resources effectively current mechanism needs to be changed.
Before change
(1) SERVAL server receives agent's GetCommand request.
(2) SERVAL server waits the timing to response (Depends on polling interval)
(3) SERVAL server responses the command related to the request.
After change
(1) SERVAL server receives agent's GetCommand request.
(2) SERVAL server responses wait-request (polling interval) or the command (if it is time) to agent.
The text was updated successfully, but these errors were encountered:
Certain fixed wait time is set (wait time = polling interval).
In case it takes us saInterval time from previous update, then executes the status acquisition.
Current polling and timeout mechanism has problems in performance perspective.
SERVAL server keeps handling particular agent connection permanently.
Therefor SERVAL server needs a lot of thread for processing agents.
Huge number of threads need huge memory resources on Linux.
In order to use resources effectively current mechanism needs to be changed.
Before change
(1) SERVAL server receives agent's GetCommand request.
(2) SERVAL server waits the timing to response (Depends on polling interval)
(3) SERVAL server responses the command related to the request.
After change
(1) SERVAL server receives agent's GetCommand request.
(2) SERVAL server responses wait-request (polling interval) or the command (if it is time) to agent.
The text was updated successfully, but these errors were encountered: