High Resource Use by wc_update_product_lookup_tables_rating_count_batch

  • Resolved Xaifu

    (@xaifu)


    1 year, 3 months ago

    Hello!

    In a WooCommerce store with 15,000 products, I perform stock imports using wpallimport every 15 minutes.

    This triggers server problems as each import initiates thousands of processes named wc_update_product_lookup_tables_rating_count_batch, often with parameters like ‘offset’ => 7850, ‘limit’ => 50. These processes consume significant server resources.

    I’m thinking of disabling the wc_update_product_lookup_tables_rating_count_batch process during ongoing daytime stock imports and scheduling it to run only once at the end of the day.

    I’m concerned about the potential impacts of this change. Would limiting the wc_update_product_lookup_tables_rating_count_batch process to a single daily execution adversely affect product rating counts, inventory synchronization, or other critical aspects of the WooCommerce store operations?

    Looking forward to receiving your guidance on this matter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @@xaifu

    The wc_update_product_lookup_tables_rating_count_batch process is responsible for updating the product rating counts in the lookup tables, which are used to improve the performance of your WooCommerce store.

    However, running this process during every stock import can consume significant server resources, especially if you have many products. Disabling this process during ongoing daytime stock imports and scheduling it to run once at the day’s end could help alleviate the server load.

    While this change should not adversely affect inventory synchronization, it might delay your store’s update of product rating counts until the process is run. This means that any changes in product ratings made during the day may not be reflected on your store until the end of the day.

    Please note that this is a significant change, and it’s recommended to test this on a staging site before implementing it on your live site.

    I hope this clarifies your concern. If you have any other questions, feel free to ask.

    Thread Starter Xaifu

    (@xaifu)

    Thank you for your response @shameemreza

    My conclusion is that since I have product ratings and reviews disabled, I can completely eliminate the wc_update_product_lookup_tables_rating_count_batch process. I assume there may be consequences that I have not foreseen, but I would just like to confirm that this process is limited to updating the count of ratings and reviews and nothing else. Is that correct?

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hello @xaifu

    Yes, you are correct. The wc_update_product_lookup_tables_rating_count_batch process is primarily responsible for updating the count of product ratings and reviews. If you have these features disabled, eliminating this process should not negatively impact other operations of your WooCommerce store.

    However, it’s always a good practice to monitor your site closely after making such changes to ensure there are no unforeseen consequences. Also, just like before, we recommend testing this change on a staging site before implementing it on your live site.

    Please don’t hesitate to reach out if you have any other questions or concerns. We’re here to help!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘High Resource Use by wc_update_product_lookup_tables_rating_count_batch’ is closed to new replies.