query performance issues on update_meta with new meta chunker

Home Forums Calendar Products Events Calendar PRO query performance issues on update_meta with new meta chunker

Viewing 15 posts - 1 through 15 (of 26 total)
  • Author
    Posts
  • #1297064
    Nicolas
    Participant

    Hello, One minute to publish a post or an event. Could you tell me how to comment meta chunked please ?

    ========================
    PLEASE LEAVE FOR SUPPORT
    Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/severe-query-performance-issues-with-new-meta-chunker/

    #1298248
    Victor
    Keymaster

    Hi Nicolas!

    Thanks for reaching out to us!

    Is the code snippet that Zach put up here the one you are looking for?

    Are you experiencing delays when publishing a post or an event? Did this started all of a sudden after an update for example?

    How many events, venues and organizers do you currently have in your site? Perhaps you can tell me more about your issue and see if we can find the source of it.

    Let us know how that goes.

    Best,
    Victor

    #1298307
    Nicolas
    Participant

    Dear Victor,

    Thank you for your kind availability.

    We use this snippet since yesterday. It perfectly resolved the issue but only with regular post and not custom ones.

    The issue appeared when you introduced a new class named meta_chunker.

    Actually, to publish an event (and before this snippet a regular post as well) is activating wp-include/meta :
    // Get meta info $id_list = join(‘,’, $ids); $cache = array(); $meta_list = $wpdb->get_results( $wpdb->prepare(“SELECT $column, meta_key, meta_value FROM $table WHERE $column IN ($id_list)”, $meta_type), ARRAY_A );

    This update causes a very long query witch hits the DB (a bunch of hundreds of ID is included inside). This burns a large amount of memory and slow down the database.

    So, is there a way to bypass chunker waiting next release ? For instance :
    function tribe_remove_post_from_chunker( $post_types ) {
    return array_diff( $post_types, array( ‘post’, ‘tribe_events’, ‘tribe_categorie’, ‘tribe_venue’, tribe_meta’ ) );
    }
    add_filter( ‘tribe_meta_chunker_post_types’, ‘tribe_remove_post_from_chunker’ );

    Thank you for your urgent and appreciate help.

    Best regards,

    Nicolas

    #1298374
    Nicolas
    Participant

    This reply is private.

    #1298451
    Victor
    Keymaster

    This reply is private.

    #1304059
    Nicolas
    Participant

    Good evening,

    When a single event is published or updated, ALL THE VENUE POSTS stored in post_meta DB are update_meta_cached !

    // Get meta info
    $id_list = join(‘,’, $ids);
    $cache = array();
    $meta_list = $wpdb->get_results( $wpdb->prepare(“SELECT $column, meta_key, meta_value FROM $table WHERE $column IN ($id_list)”,
    $meta_type), ARRAY_A );
    $id_list = ALL VENUE IDs are included !!!

    Result –> LONG AND SLOW QUERY

    Two solutions :
    1. Trash all venue posts (sniff…)
    2. Prevent publish or save to update venue posts

    Could you help me shiftly please to prevent venues’ update thanks to a snippet please ?

    Best,

    Nicolas

    #1306237
    Nico
    Member

    Hi there Nicolas,

    While Victor will continue to help you here, I just wanted to inform that we included a fix for the ‘meta chunker issue’ in our release shipped last week (release notes).

    Please let us know if you still experience issue after updating the plugins,
    Best,
    Nico

    #1306262
    Nicolas
    Participant

    Yes, unfortunatly, The last release did not fix the huge amount of venue’ id which is called by each publish of event posts or regular ones. The situation is dramatic

    #1306477
    Nicolas
    Participant

    Good evening,

    Even after the last release, when a single event is published or updated, ALL THE VENUE POSTS stored in post_meta DB are update_meta_cached !

    // Get meta info
    $id_list = join(‘,’, $ids);
    $cache = array();
    $meta_list = $wpdb->get_results( $wpdb->prepare(“SELECT $column, meta_key, meta_value FROM $table WHERE $column IN ($id_list)”,
    $meta_type), ARRAY_A );
    $id_list = ALL VENUE IDs are included !!!

    Result –> LONG AND SLOW QUERY

    Two solutions :
    1. Trash all venue posts (sniff…)
    2. Prevent publish or save to update venue posts

    Could you help me shiftly urgently please to prevent venues’ update thanks to a snippet please ?

    The situation is dramatic,

    Best,

    Nicolas

    #1308239
    Victor
    Keymaster

    Hi Nicholas!

    Thanks for coming back with all that info regarding this issue. I’m really sorry you are experiencing that.

    After making some tests on my end I could spot the query you are referring to, although I don’t experience the slow down in performace, but this might be related to the number of events/venues.

    I have logged a new report regarding this issue and the team will investigate it further. We will also try to come up for a workaround to prevent that query from loading, so we’ll keep you posted as soon as we have something.

    In the meantime, could you please let us know the amount of events and venues you currently have in your site?

    Thanks,
    Victor

    #1308307
    Nicolas
    Participant

    This reply is private.

    #1309771
    Victor
    Keymaster

    This reply is private.

    #1309969
    Nicolas
    Participant

    This reply is private.

    #1311037
    George
    Participant

    This reply is private.

    #1311167
    Nicolas
    Participant

    Dear Georges,

    Thanks for you’re the kind and reliable availability of your team !

    1. Here, the database link : /* edited by admin for security purposes

    2. Could you remove the last line on github please (/* edited by admin for security purposes) please ?

    I very hope your inquiry would fulfill soon,

    I wish you a good day,

    De vous lire,

    Bien cordialement,

    /* edited by admin for security purposes

Viewing 15 posts - 1 through 15 (of 26 total)
  • The topic ‘query performance issues on update_meta with new meta chunker’ is closed to new replies.