In some cases the NDN cache may cause a performance degradation. We should investigate the cause of this, and improve the behaviour of the NDN cache.
Metadata Update from @firstyear: - Issue assigned to firstyear
What scenarios are you are referring to? In the community we recently just saw that NDN cache had a significant improvement for some people. So I'm surprised to hear that its a problem, when I hear how its really helping others.
Metadata Update from @mreynolds: - Custom field type adjusted to defect
@mreynolds That's all the info I have right now, from a customer case. That's why I think it needs investigation first :) And any improvement we make is always a win.
Note - the performance issue between 8 and 10 is NOT the NDN cache, but that we significantly changed DN normalization in DS 9.
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4 backlog
Fix with https://pagure.io/389-ds-base/issue/49330
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 close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2339
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)