Skip to content

[1.x] perf: store scheduler timestamp in cache#4363

Merged
imorland merged 1 commit into1.xfrom
im/perf-scheduler
Feb 19, 2026
Merged

[1.x] perf: store scheduler timestamp in cache#4363
imorland merged 1 commit into1.xfrom
im/perf-scheduler

Conversation

@imorland
Copy link
Member

Fixes #0000

Changes proposed in this pull request:
Currently when the scheduler is run, it stores the last run timestamp in the DB (settings). This PR changes that to store in the cache, which is faster, and decreases the load on the DB

Reviewers should focus on:

Screenshot

Necessity

  • Has the problem that is being solved here been clearly explained?
  • If applicable, have various options for solving this problem been considered?
  • For core PRs, does this need to be in core, or could it be in an extension?
  • Are we willing to maintain this for years / potentially forever?

Confirmed

  • Frontend changes: tested on a local Flarum installation.
  • Backend changes: tests are green (run composer test).
  • Core developer confirmed locally this works as intended.
  • Tests have been added, or are not appropriate here.

Required changes:

  • Related documentation PR: (Remove if irrelevant)

@imorland imorland added this to the 1.8.14 milestone Feb 19, 2026
@imorland imorland requested a review from a team as a code owner February 19, 2026 18:32
@imorland imorland merged commit 053078e into 1.x Feb 19, 2026
686 of 777 checks passed
@imorland imorland deleted the im/perf-scheduler branch February 19, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments