Thanks!
yes this is not exactly what we expected :(
I guess it was too good to be true: reduce latency and improve
quality at the same time :)
On our side I'd say that perf was the main issue, Erik added a cache
at the backend-end level which seems to have a good impact.
Morelike queries are still routed to the new datacenter in dallas to
reduce stress on eqiad. We could maybe try to reroute them to eqiad
and see if caching is sufficient?
If it's the case I'd say that we don't need to run any A/B test.
Random questions:
Is it possible to analyze the correlation between the chosen article
and the presence of an image?
Rescoring options are slightly different for enwiki, is it possible
to have the detail for e.g. enwiki/frwiki/dewiki?
If it does not require huge effort on your side I'd say that you
could run another A/B test by disabling boostLinks, you just have to
add cirrusBoostLinks=no to api URL.
Thank you
Le 26/02/2016 00:33, Erik Bernhardson a
écrit :
ouch, that is not at all the result we were hoping
for. Just goes to show why we have to test these things and not
just take a few examples that perform badly in one set and look
to do a better job with some different options. Thanks for
putting this together!
_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l