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

Hardware Constraints #1

Open
ckapoor7 opened this issue Jul 17, 2024 · 0 comments
Open

Hardware Constraints #1

ckapoor7 opened this issue Jul 17, 2024 · 0 comments
Assignees
@ckapoor7
Labels
documentation Improvements or additions to documentation

Comments

@ckapoor7
Copy link
Collaborator

Package installation is often closely tied to specific hardware of a system. While testing the code for larger scale segmentation (~200GiB) OME-ZARR files, I note that 190GiB of CPU RAM turns out to be insufficient to run through the entire computation. As a prefix to this, I think it would be a nice idea to specify that there would be a tradeoff between system constraints and specific use cases of segmentation, which would be governed by the size of volumes.

It would be nice to specify my exact hardware specifications in the README, so that one has a clear idea of how they can scale their own system requirements and so on.
@kabilar kabilar changed the title Hardware Constraints Document hardware configuration Jul 17, 2024
@ckapoor7 ckapoor7 added the documentation Improvements or additions to documentation label Jul 17, 2024
@kabilar kabilar changed the title Document hardware configuration Hardware Constraints Jul 17, 2024
@ckapoor7 ckapoor7 self-assigned this Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ckapoor7 ckapoor7

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ckapoor7