- **status**: in-progress --> code-review - **QA**: Dave Brondsema - **Comment**:
al/7566, Search used BTreeCursor, to optimize the performance, I've replaced the find statement with count, which is much faster. For those tickets where acl is specified, I still 'find' them. The performance was slow, because you have to place all the ticket objects in memory and go through every single one of them to verify acl compatibility. I am not very sure that these acl checks are really necessary there, but to keep it backward compatible I still check for permissions for tickets with acl specified. --- ** [tickets:#7566] Milestone admin page can be very slow** **Status:** code-review **Milestone:** forge-aug-8 **Labels:** performance **Created:** Fri Jul 11, 2014 04:23 PM UTC by Dave Brondsema **Last Updated:** Tue Jul 29, 2014 10:06 PM UTC **Owner:** Alexander Luberg https://sourceforge.net/p/allura/tickets/milestones in particular is getting really slow. I suspect its due to queries for the "Progress" column for every milestone. Perhaps those can be run in a single mongo query somehow, or parallelize with threads. Or just skipped for closed milestones. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
