High CPU usage, any Cache?

Hello @egocefalo,

The plugin should not create a constant load on the server CPU.

Please contact our internal support team – https://woobewoo.com/contact-us/
We need more information on this issue.

Also read: https://woobewoo.com/documentation/help-us-to-solve-your-problem-faster/

Hi @woobewoo

I didn’t mean it’s constant, it’s just when it’s searching. I asked because other filters I have used (eg. annasta, woof which are not as half as good as yours) use an internal cache system, so they serve their filter results from it’s cache.

You do mention “Index Tables” but I couldn’t find any explanation about how they work on your documents, In the begining I thought those were some kind of “cache” but since there’s a visible use of CPU everytime the filter is used I preferred to ask you.

So, it’s not constant and I’m sure it’s not a conflict/error, it uses CPU when it’s meant to, your filter is the best I could find and works perfectly. I don’t think it’s necessary to bother your internal support team. Just a link to where your “Index Tables” are explained will be enough.

So thanks again for the plugin!

Best regards,

Hello @egocefalo,

We would like to investigate this case in more detail, perhaps this will help us make the plugin even faster. So I would appreciate it if you could contact our internal support team regarding this issue.

Index tables are the internal mechanics of the filter, the only thing the user sees from the outside is the “start indexing” button. But indexation happens automatically when you install a filter or add products. It cannot cause stress during filtration. The filter creates its own internal table with product data, which is faster than the one in WooCommerce. For this reason, the plugin doesn’t really need built-in caching.