Admin Column Performance for High-Volume and Live Data Search
Has anyone here tackled a larger-scale data updates, beyond building a fully custom grid with progressive loading in React? I’m curious if there are any plans in Admin Columns Pro for better handling of larger datasets.
I’m working with something like the dataset below, and it’s growing daily. ACP works well out of the box for smaller sets, but once you hit scale, it becomes tough to manage in the admin without building your own high-performance tools. The thing is, ACP has a great UI and workflow, until you get into larger data sets. At that point, it feels like you’re either all-in on a custom solution or constantly fighting limitations of some kind when you start to scale.
Would love to hear how others are managing this or if anything’s on the roadmap for scaling the app for larger data.
* ‘xsz_commentmeta’: ~4.2 million rows
* ‘xsz_comments’: ~8 million rows
* ‘xsz_options’: ~800 rows
* ‘xsz_postmeta’: ~5 million rows
* ‘xsz_posts’: ~900k rows
* ‘xsz_termmeta’: ~6.6k rows
* ‘xsz_usermeta’: ~4.2 million rows
* ‘xsz_users’: ~184k rows
* ‘xsz_wc_orders_meta’: ~494k rows
* ‘xsz_woocommerce_order_itemmeta’: ~100 million rows
Looking for best practices or tools to efficiently manage and display updates across datasets of this size. Any insights or approaches you’ve found effective would be greatly appreciated!
Here is a sample of what we built so far and would so much rather use ACP for this.
Thank you for your time and efforts and all the best ….
Thanks for reaching out. What you are describing is something we definitely recognize, and you are touching on an important point. When working with datasets of this size, the main limitations often come from WordPress itself and how it handles data in its default database tables, rather than from Admin Columns Pro specifically.
ACP fully operates within the WordPress framework and relies on the standard tables like posts, postmeta, usermeta, and so on. We do not use dedicated tables or custom storage structures, so we are subject to the same performance constraints as the rest of the WordPress admin.
With the number of records you are working with, certain columns can become heavier than others, especially if additional queries are required per row. When you combine that with displaying many items per page, performance issues are likely to appear.
There are a few things you might try to improve the experience:
Reduce the number of items displayed per page in the ACP settings
Temporarily disable heavier columns to identify which ones impact performance the most
Use caching where applicable, depending on your use case
Consider building custom columns with pre-fetched or optimized data if you have specific needs
We are always thinking about ways to improve ACP for larger-scale use cases, but at the moment there are no concrete plans for a dedicated high-performance mode.
Hope this gives a bit more context. Feel free to share more about your custom solution as well — we are happy to think along with you.
You must be logged in to reply to this topic.