The valueset is an array that is realloced as needed. It acts as a binary search tree for vs->sorted, which links to the valueset itself.
We've seen issues on huge entries (excess of 50,000 attributes). To support this, we should swap from a static array to B+Tree which avoids the need to qsort the structure, allows faster cache assisted look ups, and will be simpler to maintain in the code rather than rolling a custom datastructure for each issue.
Metadata Update from @firstyear: - Custom field type adjusted to defect - Issue assigned to firstyear - Issue tagged with: Complex, Performance, SDS
Metadata Update from @mreynolds: - Issue set to the milestone: 2.0.0
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.7.0 (was: 2.0.0)
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4 backlog (was: 1.3.7.0)
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/2205
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 - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.