We have an AEM 6.1 SP1 sites deployment where we are seeing exceptionally poor search performance using the OOTB /libs/foundation/components/search component.
The initial search is slow against a very small hierarchy of pages. It returns less than 20 results (in one example) which is paged 10/page. When navigating / paging back and forth between page 1 and 2 of the results we see significant spikes in CPU usage from 5% up to over 150%. Additionally, memory usage seems to climb slightly with each navigation and is either never or very slowly released.
We do not have a specific index defined for this scenario... but that doesn't seem to be the issue. Executing the same query in crx/de query screen, or through the query diagnostics indicates the same query is responding in 1-2ms.
Has anyone experienced this or have any suggestions on resolution?
Thanks.
Views
Replies
Total Likes
I am checking this with internal Adobe people.
Views
Replies
Total Likes
Got back this answer:
CRXDE light uses iteration & not query. The comparison is not valid. Index definition is a must. Sounds some thing need deep investigation & can;t ignore it. Please assist community member to reach official support channel
Views
Replies
Total Likes
For those reading this thread and want to know more about indexing -- see this GEMs session:
Views
Replies
Total Likes
Views
Likes
Replies
Views
Like
Replies
Views
Likes
Replies