[09:59:54] duesen: so https://grafana.miraheze.org/d/GtxbP1Xnk/mediawiki?orgId=1&viewPanel=48&from=now-3h&to=now still looks awful [10:00:02] we have added poolcounter [10:00:22] https://github.com/miraheze/mw-config/blob/master/GlobalSettings.php#L611 [14:39:38] urbanecm: would you mind pushing `refs/heads/sandbox/urbanecm/community-configuration` as a normal patch so that I can link to it in a permalink way? [14:40:17] you can mark it as WIP or abandon it to avoid code review if that's intended [14:40:44] Krinkle: can do, but based on Daniel's advice, i'll rewrite CommunityConfiguration in a way that doesn't require any core changes. [14:43:22] I see, ok nvm. [21:01:46] Hello [21:04:14] I came across https://www.mediawiki.org/wiki/Redis#Automatic_handling_of_job_recycling_and_abandons and the recommendation to use job runner service. Is there any difference to that than calling runJobs.php from a cron script or bash while loop? [21:05:51] I use the following bash script https://bpa.st/JWBA [21:17:40] The job queue manual page doesn't mention the redis job runner at all. https://m.mediawiki.org/wiki/Manual:Job_queue [21:19:03] Forza: redis jobrunner hasn't been supported for years [21:19:06] * RhinosF1 knows [21:19:10] * RhinosF1 is still running it [21:19:25] Forza: Redis needs the second job runner script *in addition to* the normal runJobs.php [21:20:33] It's not mentioned in the job queue page because... well... it's only needed for redis, but it's probably a good idea to mention it on that page [21:22:05] I am using redis as cache in MW, so should I also run the job runner service? [21:23:16] Forza: for a single wiki? [21:23:47] https://bpa.st/OYBA [21:23:51] Yes [21:24:17] Well two,but only one with visitors [21:24:39] Forza: I wouldn't bother. Cron + database is fine at that scale. [21:24:51] I do use redis for other things outside of MW, so it was available [21:25:48] But I don't understand the redis part of job queue. Wouldn't runJobs.php work when I have redis enabled? [21:26:09] runJobs.php still works yes, the redis service still uses it [21:26:25] Redis service [21:26:25] ? [21:26:49] Forza: When using Redis for caching, the job queue is still stored on the DB unless you explicitly set the job configuration to store the queue on Redis [21:27:33] yes the redisJobRunnerService [21:27:38] Ok. And if i do,then the cron job isn't enough? [21:27:56] If you are using the cron, you don't need to touch redis at all for jobs [21:28:04] You can just store them in the database [21:28:32] Using the Redis runner + Chron for jobs is pointless additional engineering effort [21:28:38] It will not gain you anything [21:29:13] Well it might gain you stress [21:29:29] :o [21:29:55] So my current config is using redis, if I understand right? [21:30:38] But I am not using redisJobRunnerService [21:31:04] Does that mean jobs are not executed? [21:31:28] I have no idea how you're running jobs [21:31:44] do you have a cron running them? [21:31:46] I'm running runJobs.php [21:31:54] That will work fine [21:32:10] https://bpa.st/JWBA [21:32:23] But if you're going to just use the script without redisJobRunnerService then you don't need redis [21:32:36] Even though I have redis in the $wgJobTypeConf? [21:32:49] Well no change that [21:33:06] I have no idea why you've wrote that bash script [21:33:14] Should I just remove it or change it (to what?) [21:33:19] The whole reason to use redis is you want queues [21:33:27] And can't afford Kafka [21:33:58] Actually, that bash script is on the job queue manual page [21:34:36] I would leave it at the default [21:34:54] You can use that script with the default [21:35:10] But using that script with redis as the backend doesn't make sense [21:35:18] You might as well not have redis [21:36:54] Yes I should remove redis in this case. Do I simply remove $wgJobTypeConf or do I need to change it? [21:37:15] You can just remove it [21:37:20] It'll fallback to database [21:37:53] Ok thanks [21:38:33] What I don't yet understood is if runJobs.php still works with redis job queue [21:41:13] It still works, since the redis chron service is basically spawning runJobs.php [21:49:40] Ah ok. Thank you [21:50:18] I was worried that stuff got sat in the redis queue forever [21:53:58] Would the redisJobRunnerService have an advantage of not having to open php every n seconds? [21:55:30] The service still spawns php all the time [22:00:15] Ah ok. Then definitely no profit doing that [22:00:22] Thanks :)