statuscount.cgi performance (WAS Re: Custom fields schema)

Kevin Benton kevin.benton at
Mon Jan 31 15:54:35 UTC 2005

Yes, however, MySQL (in 3.x) apparently won't use more than one index per
table.  Since there's an awful lot of data to go through to get to the point
where I can extract the necessary information, I just don't see how FAR will
work at this point without being able to sub-index.  Again, I'm glad to be
proven wrong.

Kevin Benton
Perl/Bugzilla Developer
Advanced Micro Devices
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have received
this communication in error, please notify the sender, then destroy any
remaining copies of this communication.
> -----Original Message-----
> From: developers-owner at [mailto:developers-owner at]
> On Behalf Of Max Kanat-Alexander
> Sent: Friday, January 28, 2005 4:56 PM
> To: developers at
> Subject: statuscount.cgi performance (WAS Re: Custom fields schema)
> On Fri, 2005-01-28 at 14:28 -0700, Kevin Benton wrote:
> > And if I'm taking 60 seconds to run a query at ~3K records, how will
> > that scale when it's 100K+ records?  1M+ records?
> 	Well, thankfully, with indexes, it will scale very well. The only
> problem with statuscount.cgi performance was indexes, and once we
> resolved that, it ran pretty fast, as I recall. :-)
> 	-Max
> --
> Max Kanat-Alexander
> Technical Support Manager, USA
> 2350 Mission College Blvd., Suite 400
> Santa Clara, CA 95054
> Phone: (408) 496-4500
> Fax: (408) 496-6902
> -
> To view or change your list settings, click here:
> <>

More information about the developers mailing list