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.

Sign up for GitHub

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

Jump to bottom

[Profiling] Assess the database size increase of the addition performance test_keys #372

Open
sdsantos opened this issue Jan 8, 2025 · 1 comment
Open

[Profiling] Assess the database size increase of the addition performance test_keys #372

sdsantos opened this issue Jan 8, 2025 · 1 comment
Assignees
@sdsantos
Labels
funder/otffoss2025

Comments

@sdsantos
Copy link
Collaborator

sdsantos commented Jan 8, 2025

No description provided.

@sdsantos sdsantos self-assigned this Jan 13, 2025
@sdsantos sdsantos moved this to Sprint Backlog in Sprint Planning Jan 13, 2025
@sdsantos sdsantos moved this from Sprint Backlog to Backlog in Sprint Planning Jan 20, 2025
@sdsantos sdsantos moved this from Backlog to In Progress in Sprint Planning Jan 21, 2025
@sdsantos sdsantos moved this from In Progress to Review/QA in Sprint Planning Jan 22, 2025
@sdsantos
Copy link
Collaborator Author

Each new run is increasing the size of the database by around 12 KB. It gets slightly smaller as URLs get reused, but it's a negligible reduction.

Assuming auto-run is enabled and every run is successful, that's 288 KB per day, 8.6 MB per month, 105 MB per year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdsantos sdsantos

Labels
funder/otffoss2025
Projects
Sprint Planning
Status: Review/QA
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sdsantos @hellais