Slow ticket search screen draw with RT 4.2.10 and PostgreSQL-9.4

Hi RT community,

I am testing the performance. When I pull up

Search->Tickets->New Search

as the RT superuser, it takes 6 seconds, which while not
exactly speedy, is tolerable. Unfortunately, for normal
users the time is 32s. I have attached the EXPLAIN ANALYZE
results and the plan looks reasonable. It wouldn’t be too
bad if the hit was taken just once, but everytime the page
is loaded it takes 32s. Does anyone have any ideas about
how to improve the performance? We are running RT-4.2.10
with a PostgreSQL-9.4 backend.

Regards,
Ken

search_explain.txt (4.38 KB)

Do you have a ton of users or some other CF with a lot of possible values that are only available (list in drop-down or an autocomplete field) to the RT super user?> On May 20, 2015, at 3:13 PM, "ktm@rice.edu" ktm@rice.edu wrote:

Hi RT community,

I am testing the performance. When I pull up

Search->Tickets->New Search

as the RT superuser, it takes 6 seconds, which while not
exactly speedy, is tolerable. Unfortunately, for normal
users the time is 32s. I have attached the EXPLAIN ANALYZE
results and the plan looks reasonable. It wouldn’t be too
bad if the hit was taken just once, but everytime the page
is loaded it takes 32s. Does anyone have any ideas about
how to improve the performance? We are running RT-4.2.10
with a PostgreSQL-9.4 backend.

Regards,
Ken
<search_explain.txt>