hello again, background: viewing a number of tickets results in 100% cpu, 100% memory usage, dead server. to the point where there's a script that runs every minute killing runaway httpd processes.
the problem we're experiencing is because the tickets have a LARGE number of transactions, due to a mail loop. example: SELECT COUNT(id) FROM Transactions WHERE ObjectId=30514 = 1,186 then doing a SELECT COUNT(id) FROM Attachments WHERE TransactionId=? for each of the entries in the Transactions table = 169,328 little wonder it hurt the server. does RT have any built-in mail-loop detection? is it possible to set a hard limit on the number of transactions that can be added to a ticket? for our RT install i wouldn't see any problems setting this limit to 1,000 transactions is it possible for a future version of RT to implement paging for viewing ticket transactions? for example, only show 100 transactions per page, with a "next page" button or similar navigation. thanks, byron [ byron jones [ zoom itg Internet "wakes up?" Ridicu - no carrier. [ +61 8 9389 5235 - Charles Stross _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
