Reply To: Scalability and caching ?

The plugin is generally not thought to be used with so many resources. The target is 5-10 till a maximum of 50 on a good server. But I haven’t tested out how far it’s usable and the most I’ve seen from customers are ~12.

Technically for many database entry’s it’s way faster to load all at once without any pre-selection and store them in an array as to load them after another by the ID. But that only counts if all resources are required and that’s only in the widget, forms, search form and the admin pages. So there is the potential for faster loading times on every page that isn’t if I simply only load them if needed. It’s really obvious, don’t know why I’ve build it in that way initial. Thanks for pushing me into that direction!