Performance issues occur when the repository contains more than 10,000 assets.

[manohareds]

Hi, I have implemented dynamic filtering using facet extraction. I added a few facets in the query parameters (in QueryBuilderImpl), where we extract the facets and build a map from the dataset, which is then used in the datasource.
The issue occurs when selecting a facet with a large result set (around 7–8k items), as it takes approximately 15–20 seconds to load.
Functionality: Property filter component
Goal: To implement a dynamic dropdown based on facets that updates dynamically according to the result se

[davidjgonzalez]

This is an underlying search performance problem; there's not alot that can be done in ASC - typically what you need to do is:

1. Verify that the poor performing queries are infact hitting fast indexes; if they arent, make a customer index they can hit.
2. Review your oak facet implementation/configuration: https://jackrabbit.apache.org/oak/docs/query/query-engine.html#facets
   • On the ASC search results component, i beleive there's a dialog control for setting the facet strategy if you havent already set that.

[manohareds]

Hi David,
Thank you for your response.
Our query execution time is currently around 1200 ms. We have implemented a custom Oak index with the property facets="{Boolean}true" to improve performance.
However, regarding the dialog configuration, when we enable the facet checkbox in our local or development environments, searchResult.getFacets() is consistently returning an empty result.
Based on your suggestion:

We have verified that the query is hitting the intended index.
We are also reviewing the Oak facet implementation and configuration as per the documentation: https://jackrabbit.apache.org/oak/docs/query/query-engine.html#facets

Additionally, on the ASC Search Results component, we understand there is a dialog option to configure the facet strategy. We are currently validating whether this has been set correctly.
Please let us know if there are any other configurations we should check.

[davidjgonzalez]

1200ms is very slow for a search .. is the query that slow without facets (like in Explain Query, or Query Debugger?) If it is, the index or query needs to be optimized. Can you share the query and the Explain Query output?

Can you adjust the "secure" setting on the facets config in the index? Depending on your use case you may not need it to be secure.

Also - remember that properties that have facets=true, also need to be propertyIndex=true.

https://jackrabbit.apache.org/oak/docs/query/lucene.html#Facets

[davidjgonzalez]

@manohareds any updates on this? Were you able to figure out what the core cause of the slowdown is?

[manohareds]

Hi David,
We have identified the root cause. The call to searchResult.getFacets() itself is taking around 11–15 seconds when the asset count is more than 7k-9k

[davidjgonzalez]

@manohareds great - then you should be able to review Oak index's facet configuration options to tune this.

[davidjgonzalez]

@manohareds any luck with this?