Ajax call is significantly slower on live server

@moisey Thanks for your detailed response.

I did not know about indexes before. I just added them but it only improved the performance for my development server, the performance is still bad in production, in fact I think it is slightly worse now.

Ajax calls are just really inconsistent in production. When making a smaller query, it takes 500ms to 1.5 seconds. A larger query takes 5 - 20 seconds! Not joking, 20 seconds. The same ajax call in development takes about 500-700ms.

Here is a link to one of those super long ajax calls - https://www.bungol.ca/api/filter_closed_listings/?minLat=43.56211925192369&maxLat=43.78560617695566&minLng=-79.65518145178225&maxLng=-79.15736345861819&zoomLevel=12&sold=30&pType=0&bed=undefined&bath=undefined&low=0&high=0&includePandL=false&showActiveListings=y&showSoldListings=y&showEndedListings=n&transactionType=Sale. This one took 22 seconds for me.

If the problem was in the code, shouldn’t the call times be similarly slow for both development and production? Yet it is only slow and inconsistent for production.

So then maybe it is the indexing setup. I just set it up yesterday, after I identified the performance discrepancy between development/production, so that seems unlikely.

Looking at the chart, there is abnormally high disk usage, even if it’s just 2 or 3 people browsing the site at a time. Is this a normal amount of disk usage?

I’m a newb at this, but it seems to me something is wrong with the server. The code being executed by my development/production environments are identical.

There are a couple of things to note. First off a 400ms database call, even on a local environment is actually a pretty slow and long query. You should really want these queries to be executing at less than 100ms and it’s unclear if that is a single ajax call that is 400ms, or if its the combination of all ajax calls.

The second part is that if you are dealing with slow queries what you can do is turn on slow query log on your database which will create a log file of all slow queries so you can drill down deeper and see which specific queries are slow.

Often times when you have a mismatch like this it may indicate that you have indexing setup on your local environment, but you maybe missing the indexes on your table/column on the database which would cause a significant change in query execution time. So you want to check your database tables to see that you have the same indexes setup between your local and production environments.

The last part is you mentioned everything was fine until you made a code change. Nine out of ten times the code change is what caused the problem. If you aren’t seeing any significant load in CPU or RAM, or any other system resources, and if the queries are always slow, as opposed to periodically slow, then you want to make sure that the code change isn’t at fault. So revert back to before you made the changes and try again.