New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NethCTI 3: rest api "extensions" performance improvement #5700
Comments
Cause Due to the need of clients to have the associated username for each extension, the server calculated it for each request of extensions. This was to maintain an abstraction login of independence between Solution The association is executed one time at boot by the Results of improvement Time takes by
Time takes by
|
How to test
Note: the change on rest api duration is more evident on an installation with a lot of users |
Description
On a large installation (~1000 users), the rest api
extensions
of asterisk proxy component stress the cpu and takes a long time. This can cause clients disconnection or disconnection from Asterisk server based on the available machine resources.Implementing this performance improvements represents a first step to make cti application more scalable.
Steps to reproduce
Expected behavior
Rest api have to be executed in a reasonable amount of time, based on the number of the returned extensions.
Actual behavior
The rest api take a long time an high cpu usage on the server.
Components
Cti server.
The text was updated successfully, but these errors were encountered: