search

ITISFoundation / osparc-meta-dakota

oSPARC service to run a Dakota study based on a Dakota configuration file.
0 stars 0 forks source link

Longer restart time by default #7

Closed JavierGOrdonnez closed 2 days ago

JavierGOrdonnez commented 2 days ago

I would argue that just 10 seconds for a new dakota.in file is too little - thus the "restart" argument is useless without editing the timeout argument as well. I would set to at least half hour, or probably one hour, by default -- ofc, can then be lengthened further by the user if necessary for them.

https://github.com/ITISFoundation/osparc-meta-dakota/blob/2f9ac1050ed2f767c9668d542932e2e70f517c5d/docker_scripts/main.py#L19C1-L19C33

wvangeit commented 2 days ago

I deployed a new version (0.2.2) : https://github.com/ITISFoundation/osparc-meta-dakota/pull/8

I consider the 1 hour a bit long, since it can lead to too much costs if the machines that spin would be large. But since we also do it for jupyter notebooks etc, I put it to 1 hour anyway.

JavierGOrdonnez commented 17 hours ago

great, thank you. PS atm the DakotaService has by default a small machine (4 cores, 16gb ram) so shouldnt be the case.