Page 1 of 1

performance of calculated fields

Posted: Tue 26 Jun 2007 12:52
by Ludek
Hi, I'm just trying to make some performace optimizations of my project using a profiler and I found, that the critical point is the oncalcfields-event - there are 4 simple assignments to calculated fields. Really just "myfield.asfloat := variable".
The OnCalcFields event is executed approx. 500 times and the profiler says, it takes 0,5 sec!
I think, this is really too much: one simple assignment to a calcfield takes > 0,25 millisecond (on a comp with AMD X2 and enough free memory)!
My query has pretty much fields, slightly over 100.
Is some performance optimization in this area possible? Or, is there a way to make it faster - like placing the field first in the field list, or last, or anything else?
Thanks for your help.
Ludek.

Posted: Wed 27 Jun 2007 09:57
by Ludek
I really need performance of calculated fields like in SDAC3 - filtering and sorting on calculated fields is currently nothing important for me... Is there a way to get some solution within a few days? Or do I need to switch back to SDAC3? (I hope, such switch-back is still possible after many days with SDAC4...) Many modules with calculated fields are currently unusable because of their "speed" :-(

Posted: Wed 27 Jun 2007 11:04
by Jackson
We have found a performance issue of calculated and lookup fields and fixed it.
This fix will be available in the next build of SDAC 4.

Posted: Wed 27 Jun 2007 11:13
by Ludek
I need the fast version next week on wednesday. Is there a chance, this fixed version will be released or do I have to temporarily change back to SDAC3?

Posted: Wed 27 Jun 2007 14:52
by Jackson
Most likely the new build of SDAC 4 won't be available within next week.