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

Continuous benchmark stalled #4634

Closed
joanhey opened this issue Apr 9, 2019 · 5 comments
Closed

Continuous benchmark stalled #4634

joanhey opened this issue Apr 9, 2019 · 5 comments
Assignees

Comments

@joanhey
Copy link
Contributor

joanhey commented Apr 9, 2019

https://tfb-status.techempower.com/

@michaelhixson
Copy link
Contributor

I don't think it is stalled. Right now it is going through the four variants of vibed, which each timeout after one hour of building. Hopefully we'll see new results in a half hour or so after it gets through the last variant of vibed.

From the current run's benchmark.log file:

--------------------------------------------------------------------------------
Benchmarking vertx-web-susom-postgres
--------------------------------------------------------------------------------
BENCHMARKING DB ...
Benchmark results:
Complete
BENCHMARKING QUERY ...
Benchmark results:
Complete
BENCHMARKING UPDATE ...
Benchmark results:
Complete
BENCHMARKING FORTUNE ...
Benchmark results:
Complete
vertx-web-susom-postgres: Benchmarking time: 8m 18s
vertx-web-susom-postgres: Build time: 1s
vertx-web-susom-postgres: Time starting database: 1s
vertx-web-susom-postgres: Time until accepting requests: 1s
vertx-web-susom-postgres: Verify time: 8m 56s
vertx-web-susom-postgres: Total test time: 9m 8s
tfb: Total time building so far: 4h53m 26s
tfb: Total time verifying so far: 81h14m 19s
tfb: Total time benchmarking so far: 76h26m 7s
tfb: Total execution time so far: 89h3m 25s
vibed: ERROR: Problem starting vibed
vibed: Total test time: 1h1m 0s
tfb: Total time building so far: 5h53m 26s
tfb: Total time verifying so far: 81h14m 19s
tfb: Total time benchmarking so far: 76h26m 7s
tfb: Total execution time so far: 90h4m 26s
vibed-dmd-pgsql: ERROR: Problem starting vibed-dmd-pgsql
vibed-dmd-pgsql: Total test time: 1h1s
tfb: Total time building so far: 6h53m 26s
tfb: Total time verifying so far: 81h14m 19s
tfb: Total time benchmarking so far: 76h26m 7s
tfb: Total execution time so far: 91h4m 30s
vibed-ldc: ERROR: Problem starting vibed-ldc
vibed-ldc: Total test time: 1h1m 0s
tfb: Total time building so far: 7h53m 26s
tfb: Total time verifying so far: 81h14m 19s
tfb: Total time benchmarking so far: 76h26m 7s
tfb: Total execution time so far: 92h5m 32s

@joanhey
Copy link
Contributor Author

joanhey commented Apr 9, 2019

Perhaps will be useful to try #4543, to lower that 4 hours.

@michaelhixson michaelhixson self-assigned this Apr 9, 2019
@NateBrady23
Copy link
Member

I'm not sure vibed is a good example of re-using the same dockerfile. Most of the differences happen during the build step; compiling with different configurations.

@michaelhixson
Copy link
Contributor

The run got past vibed and tfb-status shows new data now, so I'm going to close this issue. I agree that we should fix vibed at some point, but I see that as part of the always-present meta-issue of "we should fix or remove all failing frameworks".

@zloster
Copy link
Contributor

zloster commented Apr 10, 2019

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

4 participants