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

minimize RAM usage of disk uploader when extracing big disks #547

Open
codingben opened this issue Nov 4, 2024 · 3 comments
Open

minimize RAM usage of disk uploader when extracing big disks #547

codingben opened this issue Nov 4, 2024 · 3 comments

Comments

@codingben
Copy link
Member

There can be big disk images. The size of them can be 10-100gb (e.g. in Windows VMs). May be need to perform scalability testing in order to ensure that existing functionality can deal with big disk images.

@akalenyu said that CDI is using below 1gb of RAM to import disk images from container registry, and in our case, it could be also applied.

@codingben
Copy link
Member Author

Currently disk-uploader requests 3gb of memory and limits it to 5gb.

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2025
@codingben
Copy link
Member Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2025
@kubevirt-bot kubevirt-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants