Admin Ajax speed + Xdebug parameter

  • Resolved Patrick_D1985

    (@patrick_d1985)


    4 months, 1 week ago

    Hi there Daniele, two questions;

    1] When debugging some stuff on my end I noticed that DaReactions Pro is using the following;

    “‘ajax_url’ => admin_url(‘admin-ajax.php?XDEBUG_TRIGGER=xdebug_profile’),”

    Why is that? I’ve never seen an admin ajax call use it like this.
    I also dont see it being used in the plugin further. Can you tell my why this is added?

    2] Also for some reason DaReactions admin-ajax seems slow compared to other ajax calls.
    Other ajax calls seems to take max 1.5-2 seconds. Which is not weird when looking at the installation size / complexity etc.

    DaReactions (im using shortcode, see below) seems to take between 6-8 seconds. Which is a bit on the long side.

    For reference I am using this in my templates;

    <?php
    if (is_plugin_active('da-reactions-premium/da-reactions.php')) {
    global $post;
    $item_type = $post->post_type;
    $item_id = $post->ID;
    echo do_shortcode('[reactions id="' . $item_id . '" type="' . $item_type . '"]');
    }

    In the past for my own custom ajax functions I looked into shortinit and it’s options, my custom ajax calls take roughly 100-150ms. Shortly put at that point i have made possible user id and post id available and then could use $wpdb to do queries directly to the database, bypassing a lot of WordPress

    Is there something we can do to speed up the rendering of DaReactions?
    I tried the Performance for local storage but im not sure that improves the situation in my case as I am using FlyingPress/FlyingCDN for caching.

    Hope you can give some pointers ??

    Best regards, Patrick

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Patrick_D1985

    (@patrick_d1985)

    Ok let me correct the second point. It seemed another plugin was wreaking havoc to weirdly only some admin-ajax calls. Finally found out who the culprit was today; ‘Simple Link Directory Pro’ which was also causing a slowdown in our backend. We only use it for our “We support listings” but will be dropping that one … as that behavior is way out of line.

    Admin-ajax calls seems to take max 1.5-2 seconds now including DaReactions ??

    The first point, im still interested as into why the XDEBUG param.

    And If you want we could discuss if a SHORTINIT ajax call for DaReactions can be something (that could still speed the calls up quite a bit as you could bypass a lot of WP.

    Best regards,
    Patrick

    Plugin Author Daniele Alessandra

    (@danielealessandra)

    Hi Patrick,

    Thank you for raising these issues.

    1. The XDEBUG_TRIGGER parameter was used during the development of the plugin to facilitate debugging and was mistakenly left in the code. You can safely remove it, and it will not be included in future releases of the plugin.
    2. Regarding the performance of DaReactions AJAX calls, we are currently testing the implementation of SHORTINIT AJAX calls, which could significantly reduce response times. We are working to optimize the code and improve performance. We will update you soon with an improved version of the plugin.

    We greatly appreciate your feedback and continued support.

    Thread Starter Patrick_D1985

    (@patrick_d1985)

    Hi Daniele,

    Thanks for getting back to me ??

    1 – Crystal clear, it happens ??
    2 – Very cool, I think it can be doable for DaReactions and that will greatly speed it up, which for community usage (as it is for me) will be wonderful.

    If I can help in any way feel free to let me know.
    And keep up being awesome man ??

    Plugin Author Daniele Alessandra

    (@danielealessandra)

    Hi Patrick, after numerous experiments, I’ve discovered two things: first, when using SHORTINIT with a minimal version of WordPress, I have to give up knowing who the user is, and because of that, I can’t determine in advance if you’ve already voted for the content you’re viewing. Second, there isn’t much difference in response times, and unless you’re using plugins that significantly slow things down, you shouldn’t experience any noticeable delays.

    Additionally, I’ve recently released version 5.2.0, which, among other things, replaces the old filesystem-based cache system with wp_cache, improving performance a bit. Finally, I’d like to inform you that version 5.2.1 will be released in the coming days, addressing all the warnings reported by Plugin Check, which is now part of the deployment process. I’ll mark this issue as resolved.

    Thread Starter Patrick_D1985

    (@patrick_d1985)

    Hi Daniele, thanks for getting back on this.

    Yeah SHORTINIT can be a bit of a pain to get the current user. There are some ways to do this but I’ll leave that on the table if those are good ways of doing so (JS or other methods of storing the current user id for example) . And if response times remain more or less equal beyond that well then the gain of doing that is well unneeded. I was just wondering if there was something to be gained on this end.

    In regard to the wp_cache transition, speeds seems a bit better, on my larger install it takes roughly 1-1,5 s which is not bad at all.

    Ah cool to hear about the future updates coming as well, keep up the great job!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.