Caused multiple site crashes

  • Jonas

    (@gnuworld)


    3 days, 18 hours ago

    Not built with the performance or stability of larger WooCommerce stores in mind whatsoever.

    We ran this on a dedicated VPS with 8 CPU cores and 24 GB RAM, and its catalogue/feed syncing brought the site to its knees on more than one occasion.

    The plugin handles catalogue syncing, feed generation, Meta tracking and related background processes, but provides no useful control over batching, throttling or scheduling resource-intensive sync jobs.

    In our case, catalogue/feed activity coincided with extremely aggressive meta-externalads crawling of the store, including hundreds of requests per minute. Combined with the plugin’s own sync/background workload, this generated enough load to destabilise Redis/object caching and make both the storefront and WordPress admin extremely slow or unavailable. Disabling the plugin immediately restored normal performance.

    There are also numerous reports from other users involving failed feed-generation jobs, repeated scheduled-action retries, excessive CPU usage and heavy catalogue syncing.

    For a small catalogue it may be fine, but I would be very cautious about running it on a larger WooCommerce store. We ultimately replaced it with separate dedicated plugins for Meta Pixel/CAPI tracking and catalogue feed generation, giving us much better control over each process.

Viewing 1 replies (of 1 total)
  • Plugin Support iodic

    (@iodic)

    3 days, 10 hours ago

    Hi @gnuworld,

    Sorry for the disruption this caused.

    The plugin does not currently offer settings to batch or throttle product feed generation.

    The meta-externalads requests come from Meta’s web crawler rather than the plugin’s background queue. That traffic can be controlled separately through robots.txt or rate limiting at the server or CDN layer — but note that it can affect ad performance if it’s rate-limited aggressively.

    If you’re open to it, please open a support thread with your system report and the details and logs from one of the failed wc_facebook_regenerate_feed actions under WooCommerce → Status → Scheduled Actions. You can share both via Pastebin, and I’ll look into the feed-generation load separately.

    Best,
    Marko

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.