• Resolved nyehia

    (@nyehia)


    I recently migrated my store to HPOS, and I’ve ensured that all plugins are updated to their latest versions. The database is hosted on RDS Aurora Serverless on AWS.

    Since migrating and transitioning to the new HPOS mode, I’ve observed a significant spike in database capacity—from 4 units to 64 units. This unexpected increase is causing a substantial impact on my AWS costs.
    I found that if I disable “Enable compatibility mode (synchronizes orders to the posts table).”, the database is down to 4 units.

    Can you please explain why enabling this option caused this spike?


    Thank you in advance for your support.
    Noura Yehia

    • This topic was modified 10 months, 1 week ago by nyehia.
    • This topic was modified 10 months, 1 week ago by nyehia.
    • This topic was modified 10 months, 1 week ago by nyehia.
    • This topic was modified 10 months, 1 week ago by nyehia.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Noura,

    I understand you are experiencing a database capacity spike after migrating to HPOS. HPOS is a new feature that improves the scalability, reliability, and simplicity of your store by storing order data in custom tables optimized for WooCommerce queries. However, some extensions or plugins may not be fully compatible with HPOS yet and may require the order data to be synced to the _posts and _postmeta tables as well. This is why we provide the option to enable compatibility mode, which synchronizes orders to the posts table.

    Enabling compatibility mode may cause a spike in database capacity because it creates duplicate entries for each order in both the custom tables and the posts table. This increases the read/write operations and the size of your database. Depending on your hosting provider and plan, this may affect your AWS costs as well.

    To avoid this issue, we recommend that you only enable compatibility mode if you are using an extension or plugin that requires it. You can check the compatibility status of your extensions and plugins in WooCommerce > Status > HPOS Compatibility. If you see any warnings or errors, you can contact the extension or plugin developer and ask them to update their code to work with HPOS.

    If you disable compatibility mode, you will save database space and improve performance, but some extensions or plugins may not work as expected.

    I hope this helps you understand the cause of the database capacity spike and how to resolve it.

    Thread Starter nyehia

    (@nyehia)

    Thanks for your feedback Afzal, the problem is I didn’t have many orders created, just 3 orders only, so it seems unusual that the database has consistently used 64 capacity units over the past 48 hours for just 3 order synchronization with the posts table.

    Additionally, upon checking WooCommerce > Status > HPOS, I didn’t find any warnings or errors related to plugins that might be incompatible.

    Hi there @nyehia ??

    Thank you for reaching back, with further details on this.

    upon checking WooCommerce > Status > HPOS, I didn’t find any warnings or errors related to plugins that might be incompatible.

    With that in mind, having HPOS enabled without the compatibility mode at your site, should be OK.

    the problem is I didn’t have many orders created, just 3 orders only, so it seems unusual that the database has consistently used 64 capacity units over the past 48 hours for just 3 order synchronization with the posts table.

    It would be difficult to say anything without further data.

    To get an idea of how your site is configured, could you please share a copy of your site’s System Status, as exemplified here? Once you’ve done that, paste it here in your response.

    Looking forward to hearing from you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Database Capacity Spike After Migrating to HPOS’ is closed to new replies.