Subject | Re: Poor Performance |
---|---|
Author | berniebialt |
Post date | 2005-06-08T20:05:10Z |
Ann:
Thanks for respond to me. I ran gstat and here are some of the
details that I see:
Flags 0
Checksum 12345
Page Size 4096
ODS Version 10.1
Oldest Transaction 434143
Oldest Active 446334
Oldest Snapshot 446334
Next Transaction 446335
Is the issue the difference between Oldest Transaction and Next
Transaction? I noticed it is a differnce of over 12000. If this is
the problem, what would cause this to occur? and how could I keep
this from happening going forward.
Thanks,
Bernie
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:
Thanks for respond to me. I ran gstat and here are some of the
details that I see:
Flags 0
Checksum 12345
Page Size 4096
ODS Version 10.1
Oldest Transaction 434143
Oldest Active 446334
Oldest Snapshot 446334
Next Transaction 446335
Is the issue the difference between Oldest Transaction and Next
Transaction? I noticed it is a differnce of over 12000. If this is
the problem, what would cause this to occur? and how could I keep
this from happening going forward.
Thanks,
Bernie
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:
> berniebialt wrote:caused
>
> The most likely problem is garbage collection problems, usually
> by long-standing transactions and poor index selectivity. Hereare the
> things you can do to determine whether that is the problem.page.
>
> 1) gstat -h
>
> This command reads the statistics from the database header
> What you're looking for is the difference between theoldest_active
> transaction and the next_transaction. They should be within a fewabout
> hundred of each other.
>
>
> 2) gstat -a -r >stats.log
>
> This command reads the whole database, collecting statistics
> data distribution and indexes. Look first at the max version:values
> for each table. They should be no more than 10. Then check themax dup
> for indexes. Any index with a max dup over 30,000 is a potentialproblem.
>
>
> Regards,
>
>
> Ann