My popular ArticleQuality gadget is failing because requests like this are regularly taking more than 30 seconds. Original ORES would usually respond within a second or two.
It also appears there might not be any caching in place because re-loading a page where these scores are used does not result in improved performance.
Hi @Halfak, we don't have caching set up like before in ORES, it is something that we are still thinking about.
Ores Legacy does multiple parallel calls behind the scenes, it may happen that when the models are slow in computing feature extraction or the score itself the whole batch is delayed. We are probably going to work on improving performances this quarter.