We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
#656 - Tempcode optimiser
This is a spacer post for a website comment topic. The content this topic relates to: #656 - Tempcode optimiser
This is kinda implemented. A lot written here isn't really workable, because the bulk of Tempcode evaluation actually runs on shared functions that come from templates. We can't change/inline that, as it would use additional RAM in a very poor trade-off.
Never-the-less, many ideas from this are now implemented (mainly in the compilation stage, with added idea of automatically replacing some symbols with PHP operators) and it actually seems to have given a 15% performance gain. This is working well alongside other Tempcode optimisations, and as discussed, we are very effectively making it so that Composr architectural features either optimise away, or don't have any cost if chosen to be disabled.
Never-the-less, many ideas from this are now implemented (mainly in the compilation stage, with added idea of automatically replacing some symbols with PHP operators) and it actually seems to have given a 15% performance gain. This is working well alongside other Tempcode optimisations, and as discussed, we are very effectively making it so that Composr architectural features either optimise away, or don't have any cost if chosen to be disabled.