Subject | Re: [firebird-support] Sloooow query |
---|---|
Author | Daniel Rail |
Post date | 2003-06-26T11:28:57Z |
Hi,
At June 26, 2003, 06:32, Milan Babuskov wrote:
The bottleneck is in Firebird's protocol, it talks too much between
the client and the server when preparing the DML/DDL statements. A
revision of the protocol is planned for FB 2.0, to figure out how the
protocol can be improved.
compare the time it takes to retrieve the data.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)
At June 26, 2003, 06:32, Milan Babuskov wrote:
> Louis Louw wrote:With FB 1.5 RC3, it's shorter than that. It's almost instantaneous.
>> Hi!
>>
>> songlist.ID is a primary key and I just make an index for
>> categorylist.songID as well as songlist.date_played and date_artist_played
>>
>> This made the query execute in 2.4 seconds. A lot better...
>> But still not near the 0.1sec I'm used to with MySQL :(
> Are you sure it's "query execution time" ?
> If you're doing connect + exec query, then it's probably the difference
> between connection time. Firebird needs a sec or even more to establish
> connection,
The bottleneck is in Firebird's protocol, it talks too much between
the client and the server when preparing the DML/DDL statements. A
revision of the protocol is planned for FB 2.0, to figure out how the
protocol can be improved.
> Perhaps you can put timestamping code right after connect so you canI would suggest timestamping the code after the prepare phase, to
> measure the speed of the query itself precisely...
compare the time it takes to retrieve the data.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)