Subject | Improving table connect performance |
---|---|
Author | Robert martin |
Post date | 2009-05-06T21:15:54Z |
Hi
We are using the IBOQuery components and are trying to speed up the
opening time of some of our screens. I believe the queries being run
are fully optimised so we are checking component settings to see if any
performance increase can be achieved. We are manually defining the
keyrelation, the query is prepared and then opened. It is part of a
read only transaction and is marked as read only. The query does not
use * but lists all desired fields. Are there any other options I
should be looking at?
It would be nice if you could run multiple prepares without having to
actually wait for the prepare to complete, in this way you could bulk
prepare say 10 queries then open them as required without taking a
performance hit. I hope that makes sense. I don't think this is
possible is it?
I had thought of opening the queries in a thread so the screen could
open before all the queries were prepared / active. However since the
components are all on a datamodule and therefore part of the 'main
thread' thats not possible either.
Any suggestions would be greatly appreciated.
Thanks
Rob
We are using the IBOQuery components and are trying to speed up the
opening time of some of our screens. I believe the queries being run
are fully optimised so we are checking component settings to see if any
performance increase can be achieved. We are manually defining the
keyrelation, the query is prepared and then opened. It is part of a
read only transaction and is marked as read only. The query does not
use * but lists all desired fields. Are there any other options I
should be looking at?
It would be nice if you could run multiple prepares without having to
actually wait for the prepare to complete, in this way you could bulk
prepare say 10 queries then open them as required without taking a
performance hit. I hope that makes sense. I don't think this is
possible is it?
I had thought of opening the queries in a thread so the screen could
open before all the queries were prepared / active. However since the
components are all on a datamodule and therefore part of the 'main
thread' thats not possible either.
Any suggestions would be greatly appreciated.
Thanks
Rob