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

Template creation seems to reset resource allocation in study #6518

Open
Tracked by #1754
wvangeit opened this issue Oct 11, 2024 · 1 comment
Open
Tracked by #1754

Template creation seems to reset resource allocation in study #6518

wvangeit opened this issue Oct 11, 2024 · 1 comment
Assignees
Labels
High Priority a totally crucial bug/feature to be fixed asap

Comments

@wvangeit
Copy link
Contributor

wvangeit commented Oct 11, 2024

I have a study cloned from one from Antonino. It was (and is) working just fine, no memory issues etc. for several runs; Now I made a template of this study (with data included). Suddenly Javier and me had memory issues when running the EM simulation in studies created from the template (no other changes). Javier has some panel (which i don't have) to increase the resources for the s4l python runner, which seems to have solved the issue for him.

So it seems the template creation in some reset the resource allocation, which should not happen imo (especially since normal cloning seems to keep it).

This is a blocker for metamodelling, since it relies heavily on templates.

@wvangeit wvangeit transferred this issue from ITISFoundation/osparc-issues Oct 11, 2024
@wvangeit wvangeit added this to the MartinKippenberger milestone Oct 11, 2024
@wvangeit
Copy link
Contributor Author

Template id is: 2ae4b01e-8709-11ef-a023-0242ac1752b8 (fails with memory issue in EM service)
Cloned study (without templating): 96ff449e-8551-11ef-b5f6-0242ac174ade (doesn't fail in EM service)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority a totally crucial bug/feature to be fixed asap
Projects
None yet
Development

No branches or pull requests

2 participants