-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Move Redis dependency management to background tasks #915
feat: Move Redis dependency management to background tasks #915
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job with this, seeing similar results to you with generally double speed on page loads, and implementation looks sound, still 1-2s sometimes on self assessment page but better than before
6aa4754
to
19c7884
Compare
src/Dfe.PlanTech.Application/Persistence/Commands/WebhookMessageProcessor.cs
Outdated
Show resolved
Hide resolved
8ae0d09
to
1dfc3a0
Compare
tests and refactor chore: Linted code for plan-technology-for-your-school.sln solution chore: remove stopwatch chore: reawait task chore: add options to program extensions chore: amend how default options work
1dfc3a0
to
8531c70
Compare
…round-processing-for-redis-jobs
|
Overview
Changes
Minor
How to review the PR
Run the web app against a cleared Redis cache, compare load times against existing functionality.
Use a
Stopwatch
for most accurate timings. E.g. inGetOrCreateAsync
you could do something like this:Additional notes
Some initial testing of the original code, a few minor tweaks I made, and this PR:
Initial requests: 456.3ms
After removing double query - 467.366ms
Removing improer async usage, running both at same time:
422.3ms
Dependency management as background task: 230ms
Checklist
Delete any rows that do not apply to the PR.