I've accounted for where all the performance went now.
Much of it is the usual type of additional feature-loading, however there is a particular performance sink that sticks out which is calls to the Active4D pseudo-classes such as the fusebox.head and the so called 'poor man's class' .
As an example, a typical dynamic page which executes several hundred lines of Active 4D scripts by the time it ultimately completes takes a 7-8% percent performance hit just by adding 9 calls to "fusebox.head.addMetaTag".
Likeways, I have a 'poor man's class' of my own which has about 20-30 assignment calls of the form $myClass->set("sortorder";1). My 20-30 calls take another 10% out of the capacity.
So the 9 calls to fusebox.head.addMetaTag and the 20-30 calls to my poor-man's class together account for the best part of a 20% overall performance reduction (Measured in pages per minute served) at high loads.
The thing is, those tools are some of the most powerful in the whole Active4D inventory, so I won't be ditching them any time soon unless my customer finds the performance unacceptable (which they don't at the moment).
If this seems reasonable, given what's going on inside those classes, then I'll simply use those functions sparingly.
Regards Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
