Performance Issue

[fungbat@…]

I notice that the performance penalty of this plugin is quite high.

Total number of tickets in the system: 45

Performance of the Active Ticket Report:

For users who are not restricted: less than 1 second (38 matches show)
For users who are restricted: 8 seconds (3 matches show)

Is there any way to improve the performance of this plugin??

[fungbat@…]

BTW, I am using Postgres as the backend.

Thanks!

[Noah Kantrowitz]

Not that I know of. The per-ticket security checks incur a lot of overhead, even moreso for the group-based checks. It has to run the check on every ticket in the result set, and that takes time. I may add some caching for the group data at some point, but this probably wouldn't help that much. If you (or someone else) has specific ideas, please feel free to reopen this ticket. For now your best be is probably to redesign your reports, possibly using something like the Component field to lower the number of tickets in the results pre-filter.