M
marian.edu
Guest
Did had a session at last year EMEA PUG Challenge discussing about that kind of overhead especially in a (over) layered framework (OERA it’s just a reference though). The method (function) call overhead is always there regardless of parameters - the only serious additional impact is when you pass data structures by values (deep copy), in fact that is visible even for properties compared with variables due to the getter method. Most probably related to this method call overhead one can see similar overhead when using a deeper inheritance chain - super’s being called. Inlining could be an option, as well as compiler code optimisation (group assigns for instance) but as you said most will just tell you this is nothing compared to the time spent on data access and it’s kinda hard to argue on that. So guess we just need to find a balance between reusability/maintainability and performance, after all we do expect to have performance overhead when using a 4GL… otherwise we would have all written good old c code and have fun shifting memory content around 
Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...