Hi everyone, I have a question about the cost related to the use of SORTBY in FT.SEARCH.
The documentation states: “In the current implementation, when declaring a sortable field, its content gets copied into a special location in the index, for fast access on sorting”.
I would like to know if “fast access” means as fast as the default ordering based on document ids. In other words: is there any performance decrease due to the use of the SORTBY clause on a sortable field in an FT.SEARCH?
Thank you for your help!