In T353622, we moved all revscoring services to use the transparent config, e.g. calling en.wikipedia.org directly within an isvc instead of using api-ro. The remaining isvcs still use api-ro. We plan to transition all models to the transparent config eventually. In this patch, we will test the Revert Risk models with the transparent config in staging and see if there are any issues.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| ml-services: remove WIKI_URL for revertrisk isvc in staging | operations/deployment-charts | master | +4 -4 |
Related Objects
Related Objects
Event Timeline
Comment Actions
Change #1037452 had a related patch set uploaded (by AikoChou; author: AikoChou):
[operations/deployment-charts@master] ml-services: remove WIKI_URL for revertrisk isvc in staging
Comment Actions
Change #1037452 merged by jenkins-bot:
[operations/deployment-charts@master] ml-services: remove WIKI_URL for revertrisk isvc in staging
Comment Actions
Update:
I tested the Revert Risk models with the transparent config in staging. It worked without any issues. Notably, it seems that the transparent config somehow increases the performance of the revertrisk multilingual isvc. The requests per second (RPS) increased from 2.9 to 6.79 based on load test results.