There are issues with 'optimizedSql' related to hit count estimation – this code path does not use the standard estimation function in RMB but rather hard-codes a high value (99999+).
This leads to consistency issues raised as one of the problems in
We discussed two options:
1. integrate hit count estimation function with the optimizedSql
2. remove the optimizedSql code path
2. is preferably as long as there are no performance regressions. This needs to be tested. If there are performance regression approach 2. should be used instead.
The 'optimizedSql' path should return the same hit count estimation as the standard path.
This should be verified by sorting by "title" when searching through the /instance-storage/instances records.
should give the same hitcount as
Place where sortby title is used:
Please test the branch before and after changes locally using the guideline from https://wiki.folio.org/display/FOLIJET/Running+performance+test+with+%27platform-perf-test%27+locally
If the result look good, please merge in RMB and open a PR for mod-inventory-storage. When mod-inventory-storage has been merge please verify the performance using:
Any performance regressions (especially related to 'sortby title') will require reverting the code.