Subject Re: One table become very slow
Author marrtins_dqdp
Sorry, i was wrong. Gstat finished though. Isn`t taht too much pages
for 9400 records?

CLIENTS (132)
Primary pointer page: 207, Index root page: 208
Average record length: 288.79, total records: 9403
Average version length: 9.00, total versions: 27565987, max
versions: 6180
Data pages: 209068, data page slots: 209849, average fill: 86%
Fill distribution:
0 - 19% = 8042
20 - 39% = 3198
40 - 59% = 2858
60 - 79% = 3354
80 - 99% = 191616

Index CLIENTSINDEX1 (0)
Depth: 2, leaf buckets: 21, nodes: 9410
Average data length: 0.45, total dup: 8439, max dup: 365
Fill distribution:
0 - 19% = 0
20 - 39% = 1
40 - 59% = 20
60 - 79% = 0
80 - 99% = 0

Index CLIENTSINDEX2 (1)
Depth: 2, leaf buckets: 12, nodes: 9403
Average data length: 1.01, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 0
60 - 79% = 1
80 - 99% = 11

Index CLIENTSINDEX3 (2)
Depth: 2, leaf buckets: 14, nodes: 9407
Average data length: 0.00, total dup: 9398, max dup: 3991
Fill distribution:
0 - 19% = 0
20 - 39% = 2
40 - 59% = 7
60 - 79% = 0
80 - 99% = 5


--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:
>
> marrtins_dqdp wrote:
> > My table is very slow, not just a bit. It contains ~4000-5000 rows
> > (cannot tell precisly now, `couse count(*) takes tooo long)
> >
>
> If you have a copy of the database, run gstat -a -r on it and find
> the part of the report that describes the CLIENTS table. That may
> provide a clue.
>
> Good luck,
>
> Ann
>