Poor performance of message (AMP) plugin
The forums topicdiscuss some performance tests results and overall poor Tigase performance. One of the metric shows long processing in AMP plugin of 3ms or more. This seems a bit too long. As we have not experienced such a slow processing before, maybe there is some code introduced recently which may result in slow processing.
This needs to be investigated.
#1 Updated by Artur Hefczyc over 4 years ago
- Status changed from New to In QA
I think the fix I made for privacy lists should also improve performance for AMP any actually all other plugins. There is a privacy lists "filter" method called to check privacy lists on all outbound packets. It suffered from the same frequent DB calls issue. And the filter method is called within plugin thread pool, hence long processing time for plugins.