Eating CPU on Saving Event

  • Mike Turner

    (@northantsphotos)


    10 years ago

    I’ve not noticed this issue before so I am assuming its from the latest release.

    Basically when I go to save an event (and even just hitting on an existing events update button without making a change) it’s taking around 20-30 seconds to update.

    I’m on a VPS and also have a seperate shared hosting account but both have the same consequence.

    If an event is on a 1 off day, then the save isn’t so bad.

    But if the event is a weekly occurrence, performance is terrible.

    I’ve monitored the Unix processes on my VPS and can see that the update is putting a CPU thread up to 100%.

    https://wordpress.org/plugins/all-in-one-event-calendar/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Jashan

    (@jashan)

    10 years ago

    Hello,

    Our next version 2.0 will deal with performance issue.

    We strongly suggest to always give an end date to your reoccurring events. Setting them to repeat forever will cause heavy server load, leading to high load times.

    Thanks

    Davidsdesk

    (@davidsdesk)

    10 years ago

    I was nailed with a hosting bill from Rackspace four times it’s previous amount due to massive increased in compute cycles. Just discovered that each of of the misbehaving sites is running All-in-One Event Calendar with recurring events. Wow.

    Jashan

    (@jashan)

    10 years ago

    Hello,

    To resolve load time issues with 1.10.11, please FTP your site.
    Go to WP-content -> plugins -> all in one calendar -> constant.php and change

    define( ‘AI1EC_DEBUG’, true );
    to
    define( ‘AI1EC_DEBUG’, false );

    This should help.
    Take care

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Eating CPU on Saving Event’ is closed to new replies.