This particular DBPerformance error happens about once every minute from page views on wikis with ShortUrl installed.

For the record, this write is not deferred as update. Rather, it happens synchronously during the page view from a hook in the Vector skin because the interface wants to show the short url always, even if it hasn't been created yet. This is a logical restriction that can't be avoided in code unless the user interface is changed.

As such, we probably need to change the extension so that if there is no short url in the database for the current page, we must not show one. We should probably also create the short url automatically for newly created pages, from a hook during page creation, so that it will always exist for new pages. That should significantly reduce the changes of no url being shown, as I suspect that this is mostly happening in cases of a page being created and then immediately being viewed, which probably happens more often then someone viewing an older page that has never been viewed since the installation of the extension.

For the latter case, we can probably still lazily create the short url, but maybe from a deferred update or job, for the next visitor. In that case we need to think about how to handle the Varnish cache, as we probably won't want to wait a week for the next cache miss for the url to show up. I guess the job could purge the url in Varnish?

Can we just deprecate ShortUrl in favor of UrlShotener?

In T122708#5088471, @Ladsgroup wrote:

Can we just deprecate ShortUrl in favor of UrlShotener?

Discussion about this T187045.