the new RT5 looks fine for me, but I’ve got a performance problem.
We’ve added a custom Field for Customers (currently ~3000 in the list). With the new feature that allows to change fields while in overview, this custom field causes alot of html code that needs to be generated and therefore a bad performance.
I’ve tried the same query on my rt 4.4.4 and rt 5.0.0 instance. The performance is worse by factor 5 and the delivered html code for ~100 tickets is blown up from ~700kb in rt4 to ~17mb in rt5. Without the customer field, the performance is fine.
Since we don’t want to remove the customer field, there would be 2 possible solutions I can imagine:
a) a way to significantly improve the performance
b) disabling the change-field feature (preferable only for the customer field)
Any ideas how to do the mentioned solutions, or other ideas how to deal with the problem?
/edit: After knation has pointed out how to disable the inline-edit feature, it turned out this isn’t causing the performance problems. query for all active support tickets. With custom field 14 sec, without just 1 sec.
hints how to track down/solve the performance issue would be very welcome. until the upgrade this worked fine.