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

[Task] Store reports in S3 #60

Closed
Tracked by #9
andrewazores opened this issue Aug 24, 2023 · 1 comment
Closed
Tracked by #9

[Task] Store reports in S3 #60

andrewazores opened this issue Aug 24, 2023 · 1 comment
Assignees
Labels
feat New feature or request

Comments

@andrewazores
Copy link
Member

andrewazores commented Aug 24, 2023

See #9 #51 #59 . Reports are currently generated and held in-memory in a Caffeine cache. Reports are generally small so this is OK for the most part, but over time the number of reports may exert noticeable memory pressure, so some cache tuning needs to be applied. Also, reports for archived recordings are likely to be accessed infrequently, but it is still worth saving the cost of regenerating a report (requires intensive CPU and memory to generate, but only takes a very small amount of disk to store), so they should be tiered between in-memory for rapid access and in S3 alongside the source recording for later reference, or for access after the Cryostat server is restarted.

@andrewazores andrewazores added the feat New feature or request label Aug 24, 2023
@andrewazores andrewazores self-assigned this Aug 24, 2023
@andrewazores
Copy link
Member Author

Fixed in #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request
Projects
No open projects
Status: Done
Development

No branches or pull requests

1 participant