This is a good point. It’s occurring because the tables are fetched from twice, once for the content snippets, and once for the PHP snippets. I’ll see what I can do to optimise this further.
@bungeshea thank you for the update.
That would be great to squeeze some additional performance out of your plugin 🙂
If you are looking for performance, I’d recommend using object caching. The results of these queries are cached meaning that they aren’t run at all on most page loads.
@bungeshea yes, we are using it for some site i.e those that have it enabled on the web host.
However many (client sites) dont use great hosting so its an uphill battle to get the sites optimised hence why we look at everything possible to squeeze that extra little bit of performance out…
Ideally getting sites to better hosting fixes (or at the very least improves the performance) but getting clients to do this can sometimes prove to be an uphill battle… if you get what I mean…
Thank you once again for reporting this @umbrellaweb. I’ve created a fix to prevent this from happening. It’ll be included in the next plugin release.
@bungeshea thanks. look forward to the upadte 🙂