Database Scalability & Performance with Large Number of Listings

General HivePress
1

Hi team,

We’re planning to scale our HivePress-based site to thousands of listings and had a few concerns:

  1. Since all listing data and custom fields are stored in standard WP tables (wp_posts, wp_postmeta), how is performance optimized to prevent database bloat and slow loading as the data grows?
  2. Is there a way (or best practice) to use separate custom tables for listings and attributes to improve speed?
  3. Have other users experienced slowdowns with large-scale usage? Any suggestions to avoid that?

Would appreciate insights on how HivePress is structured to handle large volumes and any advice for scaling smoothly.

Thanks!

3

Hi,

  1. Yes, we use the WordPress database schema at the moment. Currently, we use internal cache for optimization (e.g. by storing taxonomy term labels as meta to prevent more joins in the query), also object cache if available. We also plan to implement the “lookup tables” that will be synced with wp_posts table to improve the search performance.
  2. Unfortunately there’s no easy way to do this at the moment. I recommend setting up caching (e.g. LiteSpeed cache), and reducing the number of search filters (these really affect the search performance) if possible. Also, I recommend keeping only required plugins as some plugins may bloat the database.
  3. This depends on many factors, e.g. the hosting plan, the number of listings and search filters, optimization measures, etc. There were no critical reports yet (most reports about the slow search were related to the booking availability search), but we’ll try to implement the “lookup tables” feature as soon as it’s possible.

Hope this helps