Issue 6183 - Slow ldif2db import on a newly created BDB backend #6208
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
droideck
force-pushed
the
ldif2db_autotune
branch
from
e41aaa2 to
f24bca0
Compare
progier389
approved these changes
Jun 10, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: 389ds#6183 Reviewed by: ?
droideck
force-pushed
the
ldif2db_autotune
branch
from
f24bca0 to
763e1a4
Compare
|
@droideck , the patch looks good to me as well but something to clarify: the tuning of the cache is missing, what specific cache (db cache, entry cache, import cache,..) ? If it is db cache, something that is not clear to me is that when the instance is created, it contains a default backend and I would expect db cache to be set. |
I have suspicions it's the DN cache, but I am not exactly sure. I can dive deeper into that if you want, though. It'll be interesting to dive into. :)
|
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
droideck
added a commit
that referenced
this pull request
Jun 12, 2024
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import. Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario. Fixes: #6183 Reviewed by: @progier389, @tbordaz (Thanks!!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Description: After creating a new BDB backend, we autotune the cache only when restarting. So, an administrator will try to import an LDIF before that; she will have a very slow import.
Fix Description: Do the autotuning during the backend creation. Add a CI test for the scenario.
Fixes: #6183
Reviewed by: ?