Replies: 2
Hi,
I run a ‘Find a lawyer’ type of website made with Bricks, ACF Pro and WP GridBuilder for filtering.
I have around 15,000 lawyers (posts) – each has it’s own page, and there is a global page where user can filter lawyers based on city, law specialization, etc. (taxonomies) with WP GridBuilder facets.
It’s working okay-ish, but I’m looking for a ways of improving it. I’m not much of a backend guy, and I found a couple of competition plugins for ACF that store it’s data in custom tables instead of a long wp_postmeta – Pods, or MetaBox (https://metabox.io/move-custom-fields-data-to-custom-tables/) towards which I’m leaning into.
But if it’ll be in a custom table, then I guess your plugin won’t optimize it’s queries.
So my question is… Do you have any idea which route would be better? Default storing of data without custom tables & your plugin, or custom tables? Is there a way for me to measure the effects of both approaches that you’re aware of?
Any help would be appreciated, thanks!
