[rt-users] request for feedback on a patch for RT 3.6.4

[Ruslan Zakirov]

Hi, brave users of RT 3.6.4.

In the mentioned version of RT I changed SQL queries we generate to
searches tickets by watchers(requestors, cc or admicc). Logic of those
queries is better now. However, I've broken performance of queries
like "Requestor = 'X' OR Owner = 'Y'", "Requestor = X OR Status = 'Y'"
and most probably other where condition on watcher is joined with
another condition using OR aggregator.

We have two ways to fix the problem. I sent one patch already to the
list, but we really need more feedback (positive or negative) to make
right choice, so I post it again.

Please do the following steps to collect feedback I need.
1) build a query (see above) in the query builder using sane values
for your setup
2) execute search and wait for results, we expect it to be very slow,
so you shouldn't wait to much
3) apply the patch
cd /opt/rt3;
cat /path/to/the/patch | patch -p0
4) stop and start web server
5) try search again

Send feedback. People who know how to deal with slow-logs, explain are
more than welcome to send additional info, but even if you don't know
how to deal with those it's ok, just send description of the system
behavior and wallclock timings.

6) revert patch
cat /path/to/the/patch | patch -p0 -R
7) stop and start web server


-- 
Best regards, Ruslan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3.6-searches_by_watchers_performance_fix.patch
Type: text/x-patch
Size: 2158 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20070803/41fc9612/attachment.bin>