Putting this in Blocked for now:
I found an issue at the gateway level (T365439) that makes it difficult for us to query the URLs of Lift Wing services without an ugly workaround in our network layer.

Otherwise, from some preliminary testing, the latency of the Lift Wing service for providing generated article descriptions seems to be on par with the previous service on toolforge, and should therefore be perfectly good for us to start consuming.

dbrant opened https://github.com/wikimedia/apps-android-wikipedia/pull/4710

The gateway API issue was fixed, so we can now continue testing the Lift Wing model. Here is an APK for anyone else who would like to try it:
https://github.com/wikimedia/apps-android-wikipedia/actions/runs/9305222379/artifacts/1552968133

From my testing so far, the latency seems to be in the same range as the previous wmcloud-hosted model. The latency is quite variable depending on the article, but the average seems to be ~3 seconds or less.

cooltey closed https://github.com/wikimedia/apps-android-wikipedia/pull/4710

@OTichonova can you do design review?

Most frequently the suggested descriptions do take around 3 seconds to load.
I found that roughly every 10 articles ->


• 1 took 8-10 seconds (which felt long)

• 1-2 took 4-5 seconds 

• the rest took around 3 seconds 



Is it possible to have all article suggested descriptions to load in around 3 seconds?

In T360581#9987790, @OTichonova wrote:

Is it possible to have all article suggested descriptions to load in around 3 seconds?

Unfortunately not; there are bound to be outlier articles that cause the model to take a little longer to generate a suggestion, and I'm not sure the model can be optimized much further at the moment.

Yes, just linking back to some old performance data to back up @OTichonova's findings: T343123#9573432. @Dbrant is right and I would advocate for launching. In parallel, the one thing that can be done is to follow up with ML Platform to see how close they are to being able to host on GPUs. That should be a silent change from your perspective if they can (no code updates needed) while having a noticeable impact on latency per T343123#9520331.

@Dbrant, okay thanks, moving it forward.

dbrant opened https://github.com/wikimedia/apps-android-wikipedia/pull/4830

@JTannerWMF The logic of showing machine-suggested descriptions is still subject to an ABC test that we had been running originally. Is this still applicable, or can it be removed?

cooltey closed https://github.com/wikimedia/apps-android-wikipedia/pull/4830