New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Learning to Rank's involvement in queries #2905
Conversation
Learning to Rank only changes the ordering of results when the query includes keywords and is ordered by relevance. It can only affect how results rank within a single page. The maximum effect it could have is to reverse the order of a page of results. The results all still appear on the same page. Site search searches with keywords (the majority of searches) are now served by Vertex AI search. The cost and complexity of running a Learning to Rank training and serving pipeline for the other use cases no longer seems commensurate with the impact. In addition to this, the training of our model has not been supervised effectively for a while, leading to a drop in the quality of the model. I therefore propose disabling the use of Learning to Rank in Search-API (this change) which allows the removal of the code to invoke the model, the pipeline that builds and deploys the model and the Terraform to support the deployment.
A side effect of this is a fall in response times for keyword queries (in particular) because we:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
This also starts clearing up the tech debt where marking the ab_test parameter is the only way to turn off LTR on an individual finder (the finder that replaced licence-finder had to do this to make the results usable) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🏅 🏆
These could be viewed in finder pages by appending `&debug_score=1` to the query string. Finder-frontend attempts to access these defensively, so they are safe to remove. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need to monitor this, as it's not used any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need these any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
These were only used as part of Learning to Rank. [Learning to rank is being removed since this change](#2905)
These could be viewed in finder pages by appending `&debug_score=1` to the query string. Finder-frontend attempts to access these defensively, so they are safe to remove. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need to monitor this, as it's not used any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need these any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
These were only used as part of Learning to Rank. [Learning to rank is being removed since this change](#2905)
These could be viewed in finder pages by appending `&debug_score=1` to the query string. Finder-frontend attempts to access these defensively, so they are safe to remove. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need to monitor this, as it's not used any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
We don't need these any more. [Learning to rank is being removed since this change](#2905)
[Learning to rank is being removed since this change](#2905)
These were only used as part of Learning to Rank. [Learning to rank is being removed since this change](#2905)
Learning to Rank only changes the ordering of results when the query includes keywords and is ordered by relevance.
It can only affect how results rank within a single page. The maximum effect it could have is to reverse the order of a page of results. The results all still appear on the same page.
Site search searches with keywords (the majority of searches) are now served by Vertex AI search. The cost and complexity of running a Learning to Rank training and serving pipeline for the other use cases no longer seems commensurate with the impact.
In addition to this, the training of our model has not been supervised effectively for a while, leading to a drop in the quality of the model.
I therefore propose disabling the use of Learning to Rank in Search-API (this change) which allows the removal of the code to invoke the model, the pipeline that builds and deploys the model and the Terraform to support the deployment.