aruggero commented on PR #3433: URL: https://github.com/apache/solr/pull/3433#issuecomment-3426297794
As mentioned, I report here the results of the benchmark that has been done: <img width="920" height="292" alt="Screenshot 2025-10-21 at 14 08 20" src="https://github.com/user-attachments/assets/48932330-4483-4f96-9c1d-fc2121137d4c"; /> We compared the current main branch containing the FV_cache for LTR with our contributed cache. We have also done a test in both situations with all caches with zero size to be sure not to slow down the query execution when not using caches at all. The first column represents the difference in milliseconds between the first query (no cache hit - miss than insert) and the second query (cache hit). The higher, the better, since it means that the cache has a great impact on reducing the query execution time. The second column represents the average time taken to execute the first query in milliseconds (the one that does not find any entry - miss than insert). The third column represents the average time taken to execute the second query in milliseconds (the one that finds an entry - hit). Finally, the last columns are the cache statistics from the Solr UI. We executed 10 pairs of queries (the first having a miss, the second a hit in the cache), each retrieving 10000 documents. We uploaded a feature store of 200 features and use a linear model that exploits these 200 features. All the results are positive. We obtain a slightly slower result when doing the "miss" query during pure reranking, but we still have a comparable query execution time. A detailed blog post about this will follow on [sease.io](sease.io) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
