Support Forums

Looking for support? You can access the support system via your account.

Forums › Forums › Search & Filter Pro › Too slow

Tagged: , ,

Viewing 10 posts - 1 through 10 (of 28 total)
1 2 3
  • seramor
    (Private)  October 10, 2014 at 9:05 pm #5842

    Hi,

    It takes like 6 seconds or so to update the results for a query on just 6 posts.

    This must be wrong. I am running the last update: 1.7.

    Is this normal? How can I debug this?
    Thanks

    Ross Moderator
    (Private)  October 14, 2014 at 4:11 pm #5935

    Hey Seramor

    Are you doing any complex queries with meta data? Or using many meta fields? These can sometimes be inefficient due to the way WP is setup.. but still, with only 6 posts it should be faster.

    If you have a link that would be useful and I can also take a look – I’m away at the moment but will check on my return.

    Thanks

    seramor
    (Private)  October 16, 2014 at 9:44 pm #6046
    This reply has been marked as private.
    seramor
    (Private)  October 17, 2014 at 10:47 am #6058
    This reply has been marked as private.
    seramor
    (Private)  October 17, 2014 at 11:05 am #6059

    Hi again,

    I am checking your demo and I get the following headers:

    1)
    POST http://demo.designsandcode.com/sfpro-movie-reviews/
    Status: HTTP/1.1 302 Found

    2)
    GET http://demo.designsandcode.com/sfpro-movie-reviews/search/?_sfm_oscar=0+10&sf_ajax_timestamp=1413540084185
    Status: HTTP/1.1 200 OK

    The first POST is different, since your demo does not attach “wp-admin/admin-ajax.php?action=get_results&paged=1”. Perhaps, this is what makes that I get a “Moved Temporarily” response while you are getting “Found”.

    Does it make sense?

    Thanks!

    seramor
    (Private)  October 17, 2014 at 11:13 am #6060
    This reply has been marked as private.
    seymourisland
    (Private)  October 17, 2014 at 5:52 pm #6085

    Hello There,

    You can use https://wordpress.org/plugins/query-monitor/ to check sql, ajax, and see where is the slow 😉

    seramor
    (Private)  October 17, 2014 at 6:48 pm #6086

    Thanks TSCLIMA, this plugin gives a lot of useful information, but I do not see anything that takes too long…

    However,
    I think that the main problem is that the first post in my domain is querying for

    POST http://www.mydomain.com/wp-admin/admin-ajax.php?action=get_results&paged=1
    Status: HTTP/1.1 302 Moved Temporarily

    instead of

    POST http://demo.designsandcode.com/sfpro-movie-reviews/
    Status: HTTP/1.1 302 Found

    In other words, I think that the current version of the plugin is attaching the string “/admin-ajax.php?action=get_results&paged=1” by mistake.

    Does it make sense?

    seramor
    (Private)  October 18, 2014 at 2:13 pm #6100

    Hi Ross,

    It does not matter what I try: searching in pages, searching in custom types and taxonomies, different filters (search box, category, author…), etc.

    It always takes about 5-6 seconds to display the results. It is the same for 50 pages than for 6 posts.

    Moreover, when searching regular pages, it seems not to submit the first POST.

    Please, could you have a look at this?
    Thanks!

    Ross Moderator
    (Private)  October 18, 2014 at 6:37 pm #6115

    Hey seramor

    Can you provide me with login details, FTP details, and the link to your search page?

    Some of your analyses is indeed correct – I need to try to figure out why there is a delay on the first post.

    Essentially, the form get gets posted – this is then parsed and validated (no query is performed) and then there is a redirect to a URL with all the relevant parameters ($_GET) – this url then takes the parameters and performs a query.

    The reason there is a difference between your version and the movie demo (wp-admin/ajax.php) is because the movie demo is in fact an out of date version – using the ajax url results in a much quicker query! (but not in this case 🙁 )

    Thanks

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 28 total)
1 2 3

You must be logged in to reply to this topic.