Subject | Re: exec. time = f(table count). f() ? |
---|---|
Author | jbouvatt |
Post date | 2005-06-30T00:02:33Z |
Thank you Ann.
Is there any additional info I can provide that could help having at
least a broad idea ?
My index looks like "OUTLETID,STATUS,VALUEDATE" where
- OUTLETID is an FK (integer)
- STATUS a flag (smallint)
- VALUEDATE a simple DATE
The table receives recorded data. VALUEDATE represents Year + Month
and each month adds around 2 Millions rows to the table.
But, as I said, any combination of values for the three fields will
always return 1000 rows at most.
Let's also consider that harddisk cannot run out of space, that the
db is regularly sweeped and that indexes are regularly recreated.
TIA.
--
Jerome
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:
Is there any additional info I can provide that could help having at
least a broad idea ?
My index looks like "OUTLETID,STATUS,VALUEDATE" where
- OUTLETID is an FK (integer)
- STATUS a flag (smallint)
- VALUEDATE a simple DATE
The table receives recorded data. VALUEDATE represents Year + Month
and each month adds around 2 Millions rows to the table.
But, as I said, any combination of values for the three fields will
always return 1000 rows at most.
Let's also consider that harddisk cannot run out of space, that the
db is regularly sweeped and that indexes are regularly recreated.
TIA.
--
Jerome
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:
> jbouvatt wrote:according
> >
> > Is there some function to calculate the query execution time
> > to the size of the table ?Performance
>
> Sorry, no, not even with the information you supplied.
> depends on a lot of issues, including how the data is stored, how
> compressible it is, how compressible keys are, etc.
>
>
> Regards,
>
>
> Ann