Skip to content
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

Performance Benchmarks #90

Open
chrisK00 opened this issue Aug 15, 2023 · 0 comments
Open

Performance Benchmarks #90

chrisK00 opened this issue Aug 15, 2023 · 0 comments
Labels
feature Investigate Study around a wanted feature

Comments

@chrisK00
Copy link
Contributor

chrisK00 commented Aug 15, 2023

I am considering adding a new feature to this year's roadmap that should improve the overall performance of the application by storing the NextPayment date in the database on all writes instead of calculating it every time a subscription is fetched. Completing this issue would then open up an issue for making a PoC that investigates the performance improvments doing the mentioned feature.

Requirements

  • Add a new project that makes use of https://github.com/dotnet/BenchmarkDotNet
  • We do not want benchmarks inside of unit tests that could potentially fail because of random things. We only want to log the results of the benchmarks. This can maybe be done by exporting the benchmarkdotnet to a json file and logging that result in github actions using a Powershell script that parses the json file and produces an easy to read result
  • Add at least one benchmark for SubscriptionsCalculator.GetNextPaymentDate
@chrisK00 chrisK00 added feature Investigate Study around a wanted feature labels Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Investigate Study around a wanted feature
Projects
None yet
Development

No branches or pull requests

1 participant