Slow performance and button next about atrocore HOT 2 OPEN

I did some testing on API performance myself using xdebug profiler. In our case ~25% of the time was spent in OrmMetadata::getData. TIme probably depends on the complexity of user defined entities. But if I just wrap the call and use the DataManager Cache I see substantial performance improvements.

If the cache is stale / has been cleared most time is spent in Util::toCamelCase (including the preg_replace_callback which in itself is rather expensive). In our case toCamelCase contributes to 44% of the overall calculation time. toCamelCase is beeing called more than 1M times during the first API call without cache. It seems like it is being called on every translation object. So as fas as I can tell the inputs into toCamelCase are mostly repeating. Storing the results in a lookup array would probably make things faster.

from atrocore.

I also noticed extremely poor performance since some months e.g. when logging in or using the system for a while. Clearing the cache/using a new browser tab help. @rratsun Do you have any idea on this?

from atrocore.