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

[Roy El-Hames]

Rus;

Just applied the patch a query similar to the below:
- before the patch I stopped  it after 3 minutes no results,
- after the patch it returned the correct results within seconds ..

Regards;
Roy


James Moseley wrote:
>
> (  Status = 'new' OR Status = 'open' ) AND  (  Cc.Name = 'user' OR
> AdminCc.Name = 'user' )
>
> After applying the patch, the same search takes 1 second.  This with a
> database of around 14,000 tickets.
>
>
> James Moseley
>
>
>
>
>                                                                            
>              "Ruslan Zakirov"                                              
>              <ruz at bestpractica                                             
>              l.com>                                                     To 
>              Sent by:                  "RT users"                          
>              rt-users-bounces@         <rt-users at lists.bestpractical.com>  
>              lists.bestpractic                                          cc 
>              al.com                                                        
>                                                                    Subject 
>                                        [rt-users] request for feedback on  
>              08/03/2007 11:25          a patch for RT 3.6.4                
>              AM                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>
>
>
>
> 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.
> (See attached file: 3.6-searches_by_watchers_performance_fix.patch)
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
> ------------------------------------------------------------------------
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com