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

get runtime under controle #18

Open
Eh2406 opened this issue Sep 19, 2017 · 0 comments
Open

get runtime under controle #18

Eh2406 opened this issue Sep 19, 2017 · 0 comments

Comments

@Eh2406
Copy link
Contributor

Eh2406 commented Sep 19, 2017

According to the logs:
in run497 (8170c96) time per iteration was 873.65 s - 1063.40 s taking abort 7 h all toled.
in run498 (1f5ca2e) time per iteration was 887.42 s - 1234.78 s taking abort 8 h all toled.
in run499 (568d10e) the logs where lost.
in run500 (2903ac0) time per iteration was 1573.58 s - 1681.25 s taking abort 12 h all toled.
run501 was canceled because it was taking to long.
run502 has bean running for 12 h already and is not quite done.

We can work with 12 h, now that we know, but we cant go much longer and still do overnight runs.

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

No branches or pull requests

1 participant