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

Modkit 50 GB resources per default? #5

Open
hoelzer opened this issue Oct 29, 2024 · 1 comment
Open

Modkit 50 GB resources per default? #5

hoelzer opened this issue Oct 29, 2024 · 1 comment
Labels
question Further information is requested

Comments

@hoelzer
Copy link
Member

hoelzer commented Oct 29, 2024

That is quite a lot - necessary?

E.g. thinking about someone running the pipeline on a laptop

@hoelzer hoelzer added the question Further information is requested label Oct 29, 2024
@hoelzer
Copy link
Member Author

hoelzer commented Nov 1, 2024

Maybe it is then also a good idea to use your pipeline with -with-report rep.html cpu / ram usage (may cause errors) from time to time and look at the report. To optimize RAM usage for modkit, other processes, ... It might then also make sense to split up the label again bc maybe there is only one modkit process that uses a lot of RAM but the other steps are less RAM intense. We could then have two labels:

modkit_high_ram
modkit_low_ram

for example. Using the same container but requesting diff resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant