Sybase and/or MSSQL?

[Daniel Berlin]

On Wednesday, May 21, 2003, at 07:57  PM, David Miller wrote:

> On 5/22/2003 9:40 AM +1000, Arthur Barrett wrote:
>
>> Hi all,
>>
>> I posted here a couple of months back for information on using 
>> Bugzilla with
>> a Sybase or MSSQL database.
>>
>> I got some great feedback (thanks) - the most notable of which was 
>> that
>> there were some changes coming that I should look out for.
>>
>> Have these turned up?
>
> They haven't yet.  I'll probably get some of them up one of these days 
> but
> no idea how soon.  Every time I try, some other "emergency" comes up 
> that I
> have to fix instead of porting the patches out. :)
>
> I will tell you that performance SUCKS with Sybase, compared to MySQL, 
> at
> least with the existing Bugzilla code.

Welcome to the wonders of sucky time-consuming query plan generators.
I've seen other DB's that do this, i just try to avoid them like the 
plague.

>  Sybase seems designed for dealing
> with HUGE amounts of data, and the only places we deal with a huge 
> amount
> of data is in buglist.cgi (and Sybase does buglist.cgi pretty well).
> Everywhere else we're dealing with little tiny bits of information...
> Sybase will spend 13 seconds analyzing and generating a query plan for 
> a
> query that takes .5 seconds to run once it actually runs it, and MySQL 
> runs
> the same query (including plan generation) in that same .5 seconds 
> (this is
> the query that loads an individual bug for the show_bug page).  So now
> we're doing things like moving static queries into stored procedures

Does Sybase have a prepared query type deal you could use?
Then you could use dbi's prepare_cached rather than stored procedures.

That + sharing DBI instances between bugzilla instances should make it 
fast enough.