-
Notifications
You must be signed in to change notification settings - Fork 2
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
include
impacts performance
#287
Comments
Previous chat discussion (in German). BTW: I would consider this a bug, but that's certainly debatable. |
Fixing this may help fixing hbz/lobid-resources#1666. |
- includeBenchmarkBase1: 3.2375 +/- 0.0193 - includeBenchmarkBase1000: 3.5835 +/- 0.1132 - includeBenchmarkBase100000: 5.4308 +/- 0.1477 - includeBenchmarkSome1: 3.6988 +/- 0.0185 - includeBenchmarkSome1000: 3.9415 +/- 0.2000 - includeBenchmarkSome100000: 7.8708 +/- 0.1882 - includeBenchmarkMany1: 5.1312 +/- 0.0764 - includeBenchmarkMany1000: 5.5572 +/- 0.2899 - includeBenchmarkMany100000: 17.6438 +/- 0.0740
- includeBenchmarkBase1: 3.3080 +/- 0.0558 - includeBenchmarkBase1000: 3.4018 +/- 0.0212 - includeBenchmarkBase100000: 5.4032 +/- 0.0494 - includeBenchmarkSome1: 3.7932 +/- 0.1135 - includeBenchmarkSome1000: 3.8172 +/- 0.0428 - includeBenchmarkSome100000: 6.1055 +/- 0.1947 - includeBenchmarkMany1: 5.2958 +/- 0.2262 - includeBenchmarkMany1000: 5.3335 +/- 0.3680 - includeBenchmarkMany100000: 7.7365 +/- 0.1504
Don't know if this can be closed @blackwinter ? With #327 we gained at least some performance. |
Ultimately, @TobiasNx has to decide whether his use case has improved sufficiently. I didn't link the pull request to this issue intentionally. The next step would need to be to look at the |
It seems that it got 30 min faster. |
That's roughly 3.5 %. |
In my opinion the first step is done and it improved the performance. |
A fix transfomation in one file is faster and needs less storage when executed than a fix transformation that is distributed over multiple files and combined via
include
-functions.The text was updated successfully, but these errors were encountered: