Subject | Re: rdb$procedure_parameters non index read |
---|---|
Author | ma_golyo |
Post date | 2012-01-10T09:36:12Z |
I dont't know how to measure the non index read time consumtion. (because as I write earlyer I don't know what can cause that)
I don't say that the non index read itself is the cause of the 12 sec run.
The question is, the non index read is a firebird engine bug or not?
(I think standard DDL command shoud ALWAYS read via indicies in the background.)
I don't say that the non index read itself is the cause of the 12 sec run.
The question is, the non index read is a firebird engine bug or not?
(I think standard DDL command shoud ALWAYS read via indicies in the background.)
--- In firebird-support@yahoogroups.com, Dmitry Yemanov <dimitr@...> wrote:
>
> 10.01.2012 11:15, ma_golyo wrote:
>
> > Currently the non index read count is over 30K, and this is just a simle
> > (few database object) test case.
> > Index reads means less record read -> less I/O -> faster execution.
>
> Sure, but if these non-indexed reads occupy e.g. less than 10% of the
> overall execution time, it makes a lot of sense to ignore them.
>
> > Query
> > ------------------------------------------------
> > execute procedure dbschema_vc
> >
> > Query Time
> > ------------------------------------------------
> > Prepare : 47,00 ms
> > Execute : 11 766,00 ms
>
> 30K sequential reads cannot last for 12 seconds, so I believe the real
> problem is elsewhere.
>
>
> Dmitry
>