Subject | Re: [IBO] 2 strange situations |
---|---|
Author | Geoff Worboys |
Post date | 2001-05-10T04:51:29Z |
Hi Carlos,
Have you checked the plans issued when you prepare the statement? (To
be sure none of the joins are using natural).
The SchemaCache will only help on 2nd and subsequent connnects, did
you check this? In fact, even without SchemaCacheDir you should
normally find that the second time you open the form (in the same
application session) that it significantly faster **IF** the problem
is related to initialisation of schema cache details. If this is not
the case, then we can ignore the SchemaCache as the cause of the
problem.
I find Interbase is often quite slow for the first few requests after
starting up. Are you sure your server is not dying (check the
interbase.log).
The IB_Profiler dialog may help show where the problem is - I've not
had much experience with it myself, but it does give some interesting
details that may help.
If the delay re-occurs after a few seconds as you describe, I am
wondering if it is due to IBOs background work in retrieving
additional records. You can check this by disabling the OAT
management for the transaction (set Transaction.TimeoutProps.Attempt
:= 0).
I cant think of much else to try at the moment.
Geoff Worboys
Telesis Computing
Have you checked the plans issued when you prepare the statement? (To
be sure none of the joins are using natural).
The SchemaCache will only help on 2nd and subsequent connnects, did
you check this? In fact, even without SchemaCacheDir you should
normally find that the second time you open the form (in the same
application session) that it significantly faster **IF** the problem
is related to initialisation of schema cache details. If this is not
the case, then we can ignore the SchemaCache as the cause of the
problem.
I find Interbase is often quite slow for the first few requests after
starting up. Are you sure your server is not dying (check the
interbase.log).
The IB_Profiler dialog may help show where the problem is - I've not
had much experience with it myself, but it does give some interesting
details that may help.
If the delay re-occurs after a few seconds as you describe, I am
wondering if it is due to IBOs background work in retrieving
additional records. You can check this by disabling the OAT
management for the transaction (set Transaction.TimeoutProps.Attempt
:= 0).
I cant think of much else to try at the moment.
Geoff Worboys
Telesis Computing