Change Details

As you can see in the screenshot below, when the assessment parser function was embedded in the master assessment template on English Wikivoyage, it caused a large spike in database inserts and some short-lived spikes in database lag.

As you can see in the screenshot below, when the assessment parser function was embedded in the master assessment template on English Wikivoyage, it caused a large spike in database inserts and some short-lived spikes in database lag (up to 5 seconds): {F4442395} This was deemed unacceptable by the DBAs, so we need to find a way to smooth out these spikes before we can roll-out PageAssessments to English Wikipedia. There are at least 3 possible solutions here: 1. Slow down the automatic reparsing of pages when their caches are invalidated by template edits 2. Slow down the processing of the refreshLinks job (by changing how it is handled by the job runner or changing how all low priority jobs are handled) 3. Move PageAssessments database interactions back to their own job and make sure the job runner runs that job slowly (perhaps by creating a new 3rd class job designation). This isn't really a new problem, but is the same sort of database interaction that arises from adding a category or link into a heavily used template, so I'm guessing that solutions #1 or #2 are going to be preferable. I'm looking for advice from the #performance-team on the best way forward, and depending on the choice, help implementing that solution.

As you can see in the screenshot below, when the assessment parser function was embedded in the master assessment template on English Wikivoyage, it caused a large spike in database inserts and some short-lived spikes in database lag. lag (up to 5 seconds): {F4442395} This was deemed unacceptable by the DBAs, so we need to find a way to smooth out these spikes before we can roll-out PageAssessments to English Wikipedia. There are at least 3 possible solutions here: 1. Slow down the automatic reparsing of pages when their caches are invalidated by template edits 2. Slow down the processing of the refreshLinks job (by changing how it is handled by the job runner or changing how all low priority jobs are handled) 3. Move PageAssessments database interactions back to their own job and make sure the job runner runs that job slowly (perhaps by creating a new 3rd class job designation). This isn't really a new problem, but is the same sort of database interaction that arises from adding a category or link into a heavily used template, so I'm guessing that solutions #1 or #2 are going to be preferable. I'm looking for advice from the #performance-team on the best way forward, and depending on the choice, help implementing that solution.