Nice but…

  • It is nice, but it uses way more cpu and executions. Everything went RED on the server provider.

    CPU Time Usage before the plugin last 2h: MAX 2000/4000
    CPU Time Usage with the plugin last 2h: 30.000/4000

    Account Executions before the plugin last 2h: MAX 2500/4000
    Account Executions with the plugin last 2h: MAX 40.000/4000

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hello @tasosnat,

    Thanks for reporting your experience with WooCommerce Admin.

    Did you see the CPU usage spike after starting a historical import? If so, that rise in CPU usage should only last for the duration of the import, which creates reporting table data for all of your Customers and Orders.

    Once the import is complete, the report tables are updated on a per-order basis and shouldn’t demand much processing time.

    Thread Starter tasosnat

    (@tasosnat)

    Hello @jeffstieler

    I can tell you exactly when the cpu spike is happening. Everytime a change take place on woocommerce ( order changed from processing to complete, from pending payment to processing etc). That’s all i can guess because the cpu spike is happening on working hours 9-5 when we process the orders.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Nice but…’ is closed to new replies.