Possible to find the source of the elasticsearch queries?

[mishav]

@makingthingsapp

elasticsearch

I think it was @josh mentioned in one post that the backend is no longer using elastic search, and its named that way for backwards compatibility.

@makingthingsapp

Some of the responses are quite big, and contain a lot of data that is not needed for the page.

@josh mentioned in a another post that returning the results from a search not only returns all fields for the matching rows, but also all matching rows for any referenced thing.

For example, if User has field UserOrders (list of type Order), a search on Users will return the matching users, plus the full details of each of their Orders, plus any thing referenced by Order.

Performance Q&A guide

I’m going to be checking this thread periodically over the next week to answer questions on performance best practices, inspired by (among other people who have asked for this): This will probably get turned into a performance section in the manual, but I figure the forum is a good place to kick things off. I have to run for now but will chime in later today with some general tips + answers to blueback09’s questions above.