We are constantly calling configuration get functions during a connection. These calls are expensive, so we should just store all these settings in the conn struct during handle_new_connection() I feel having a static config (ioblocktimeout, etc) throughout the lifetime of a connection is an acceptable tradeoff.
For a SRCH req, ioblocktimeout is fetched twice per returned entries. This change contributes to better perf. It can be extended to idletimeout, theadperconn.
Metadata Update from @tbordaz: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
https://pagure.io/389-ds-base/pull-request/50312
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
385158000..c9d65282d master ab94fc12e..117d4ba09 master
After c9d65282d05f1b543e171e4b81efb9a4789e778b nsslapd-maxbersize is no longer limiting client connections. Test dirsrvtests/tests/suites/config/config_test.py::test_maxbersize_repl fails.
nsslapd-maxbersize
dirsrvtests/tests/suites/config/config_test.py::test_maxbersize_repl
Metadata Update from @vashirov: - Issue status updated to: Open (was: Closed)
Fix regression from using the wrong integer type:
9ebf5f8a2..26b9e1b01 master -> master
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3365
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)