Page 1 of 1

calculated fields - performance problem

Posted: Fri 10 Jun 2011 21:58
by civic9
Hi,

We have performance issues with your driver under RAD XE when using calculated fields and an additional query in the OnCalcFields event. The same code under BDS 2006 with older driver works many times faster.
Can you investigate this?

Execution times:
1. BDS 2006, C++
Calc fields enabled - 2 seconds
Calc fields disabled - 1 second

2. RAD XE, C++
Calc fields disabled - 2 seconds
Calc field enabled - 25 seconds (!!!)

Download the sample app from:
http://www.netinfo.pl/oracleCalcFieldsTest.zip
In the zip file you will find:
CFTSourceCodeBDS2006.zip, CFTSourceCodeXE.zip - source code of sample apps (the same in both environments)
ObjectsSql.sql - sql script to create sql schema and insert sample data;
OnCalcFieldsTestBDS2006.exe, OnCalcFieldsTestXE.exe - compiled sample apps
dbexpoda30.dll, dbexpoda40.dll - your oracle dbexpress drivers

Posted: Fri 17 Jun 2011 01:25
by civic9
Hi,

AlexP - could you check the problem described above?
do you need more info?

Posted: Fri 17 Jun 2011 07:42
by AlexP
Hello,

Thank you for the information. We've reproduced this problem. Now we are investigating the possibilities of such dbExpress behaviour on different IDE versions.
When we have any results, we'll let you know.

Posted: Fri 17 Jun 2011 09:18
by civic9
Thanks,

We have checked this again using dbexpoda30.dll from dbxoda 4.90.0.25 under bds2006 - performance is like under rad XE too (>20 seconds). So, this is not different IDE version issue, I think.

dbexpoda30.dll v.4.20.0.8 works well (but we can use this version only under bds2006).

Posted: Tue 02 Aug 2011 20:56
by civic9
Hi,

are you going to fix it in the next build?

Posted: Wed 03 Aug 2011 09:13
by AlexP
Hello,

We are still working on this problem.
We will try to fix it in the next version.

Posted: Wed 24 Aug 2011 12:25
by civic9
still not fixed in 5.00 beta.

we are waiting almost 3 months.
seriously - are you going to fix it?

Posted: Mon 05 Sep 2011 11:24
by AlexP
Hello,

We have fixed the problem.
This fix will be included in the next build.