Slow ldif2db import on a newly created BDB backend

[droideck]

Issue 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. The workaround is very simple - restart after the new backend is created.
So we either need to:

• modify the CLI (or the core backend creation code)

OR at least

• modify our CI tests so they restart the instance after the backend is created but before the restore/ldif2db.

Steps to Reproduce Slow Import
Steps to reproduce the behaviour:

1. Install an instance
2. Create a new backend
3. Stop the instance
4. Run ldif2db on the new backend - It's very slow.
5. Start the instance

Steps to Reproduce Fast Import
Steps to reproduce the behaviour:

1. Install an instance
2. Create a new backend
3. Restart the instance (Autotuning is performed)
4. Stop the instance
5. Run ldif2db on the new backend - It's fast enough.
6. Start the instance

[droideck]

https://issues.redhat.com/browse/RHEL-5131