(meta note)

Just a heads up, this task is currently public and not restricted to WMF-NDA

(top left)

Open, Normal Public

If I edit task and set the visibility to only WMF-NDA then it will be visible to WMF-NDA only. Projects are confusing and the fact they can be used as objects across multiple functions: CC, projects, ACL objects, etc.

I am going to set this task as visible to WMF-NDA only to demonstrate :)

(now...top left)

Open, Normal WMF-NDA

tx @chasemp

I checked the query

SELECT /* Wikimedia\Rdbms\Database::select www-data@mwmain... */  DISTINCT( pa_project_id )  FROM `page_assessments

Based on the file /srv/mediawiki/dblists/pageassessments.dblist the enwiki, enwikivoyage, testwiki databases were used. Here are the results. I don't know which database would be queried this way but I was supposing vslow.

enwiki wasn't fast, but 3 seconds is way better than 10

i'd like to add the owner of the script as a subscriber, but I don't know how to find who is it

In T208231#4803855, @Banyek wrote:

i'd like to add the owner of the script as a subscriber, but I don't know how to find who is it

git blame can help

@kaldari if you need any help for further debugging this, you can ask me

@Banyek - Thanks for the ping. I don't think anything is unexpected here. This particular clean-up routine is expensive, which is why it was put in a cron job. Is there anything I can add to the script to indicate that? If we need to get it running faster than 3 seconds, let me know.

I think we should adjust the slow timer in a way of not to alert if the scripts runs for n seconds

This has evolved into fatals: T219935.

This is interesting. T219935 seems to indicate that the query is now poorly formed instead of just expensive. I'm taking a look to see if I can see an obvious regression.