toan added a comment.
In T255259#7266601 <https://phabricator.wikimedia.org/T255259#7266601>, @Lucas_Werkmeister_WMDE wrote: > My assumption was that, with a sufficiently high job run rate, you could run large Wikibase imports, and each edit API request would on average run as many jobs as it enqueued, keeping the job queue within reasonable limits. But that’s clearly not the case: `$wgJobRunRate` is for regular page views (`index.php`), and any wiki which doesn’t have a sufficiently high volume of page views will just accumulate more and more jobs. “Write-only” or “API-only” (or “-mainly”) wikis must have a dedicated job runner. What would be a good next step here, I'm not sure the AC for either/or applies any more with this information? The `$wgJobRunRate` and runJobs.php alternative is already mentioned in the release notes T276905: Update 1.35 release notes to mention runJobs.php and consider maybe tweaking job frequency <https://phabricator.wikimedia.org/T276905> but I'm not aware of any further documentation on running a separate job-runner for wikibase. Seeing that api requests don't run jobs (and i guess this might be where most of the wikibase traffic goes) do want to offer some examples on how to run a separate job-runner for the docker images? TASK DETAIL https://phabricator.wikimedia.org/T255259 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Lucas_Werkmeister_WMDE, toan Cc: toan, Lucas_Werkmeister_WMDE, danshick-wmde, Samantha_Alipio_WMDE, Addshore, Aklapper, Invadibot, maantietaja, Akuckartz, Iflorez, alaa_wmde, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
