Nando Dessena wrote:

> Maurice,
>
>>> So, I guess the solution for your issue has to pass through analysis
>>> of the SQL query or queries you are executing, their PLAN, the
>>> database structure (indexes, etc.) and possibly database statistics
>>> (run gstat -h on the database and report back here).
>
>> No idea what you are trying to ask but here is the gstat -h on the
>> database...
>
> the stats look more or less OK (I assume you don't need forced writes
> in your configuration).
>
> I'll try to explain myself better.
> If your fb processes are consuming CPU, either they are doing it
> because they need it to perform the jobs you are throwing at them, or
> they are suffering from one of the problems outlined above:
>
> 1) scanning indexes with lots of duplicates.
> 2) scanning records with many backversions (i.e. garbage).
> 3) sorting (much less than the other two items).

Maurice,

Something you can do to identify if you are suffering from #1 or #2 in
Nando's list is to run gstat -r -a against your database and then look
at the max dup on indexes and max versions on tables. For some
discussion about what all the output of gstat -r -a means, refer to this
thread in the archives:
http://groups.yahoo.com/group/firebird-support/message/61993

-Kevin


CONFIDENTIALITY NOTICE:
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.