This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Michael Veksler <VEKSLER at il dot ibm dot com>
- Cc: gcc at gcc dot gnu dot org, Giovanni Bajo <giovannibajo at libero dot it>, themis_hv at yahoo dot co dot uk
- Date: Mon, 30 May 2005 09:17:22 -0400
- Subject: Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
- References: <OFE450020B.CF4FD225-ON43257011.0019B0C9-43257011.001B6120@il.ibm.com>
On Mon, 2005-05-30 at 07:59 +0300, Michael Veksler wrote:
>
>
>
>
>
> Daniel Berlin <dberlin@dberlin.org> wrote on 30/05/2005 06:41:54:
>
> > On Sun, 2005-05-29 at 12:50 +0200, Giovanni Bajo wrote:
> > > Michael Veksler <VEKSLER@il.ibm.com> wrote:
> > >
> > > > 3. Nontrivial search of GCC Bugzilla are, sometimes,
> > > > extremely slow (over a minute).
> > >
> > > 3 could be worked on (Daniel?)
> >
> > Send me the URL's for the buglists and i'll look at the queries (The url
> > for the buglist contains the query).
> >
> > A lot of this is mysql's query engine being stupid, and is hopefully
> > fixed in 4.x or 5.x (sourceware is still on 3.x).
> >
> > I'm happy to optimize the searchs as best i can (by adding lame extra
> > indexes if necessary :P)
>
> It is difficult to reproduce because behavior changes over time.
> 2 hours ago I was getting time-out even for:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21808
This may be server load in that case (new hardware is in the process of
being acquired).
>
> Now, it takes about 2 seconds.
>
> Here is a synthetic test query that take only 15 seconds ATM:
>
> http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=float-store+ICE&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=CLOSED&emailassigned_to1=1&emailreporter1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=
Comment searches don't currently take advantage of the fulltext index on
the comments, and mysql isn't particulary good at them.
I'm looking into it.