Markus Junginger
Markus Junginger
Depends on the query... 3-4 seconds execution time (long) suggests that the indexed property does not help much in reducing the result count.
Your *primary* order is bytSongWordCount, correct? Also what is the typical distribution of bytSongWordCount? This is relevant in finding a workaround, as indexes are not used in your use case.
Basic idea outline: 1. use PropertyQuery to find maximum and minimum value of bytSongWordCount 2. adjust your main query to have a `equal` condition on bytSongWordCount 3. loop from maximum...
bytSongWordCount seems bad to divide your data in smaller pieces. Do you need it or could there be other ways? For, example, if you search for a single letter string...
Thanks for providing some sample data. It looks like bytSongWordCount is the size of strSongPinYin. Correct? In that case, maybe it would be possible to 1) merge bytSongWordCount as a...
> the query will loop 800 times, the speed dropped drastically Sorry, I don't understand what you are implying here. It's getting slow because... ?
> .equal(SongItemAllNew_.searchKey, i+j) Side note: I guess your search key rather is something like `(i
OK, I was not aware that you need to scan that many search "buckets" (search key values) to fill up results until you hit 120 items... Some buckets also seem...
> I also found that the maximum was 21 in this test, but there were only a few from 15 to 21 This also means that those **additional query criteria**...
Btw, we have plans to make filters more universal in the future.