#47909 Investigation on the entry cache performance
Closed: wontfix 3 years ago by spichugi. Opened 9 years ago by nhosoi.

Many functions in the entry cache code call cache_lock to protect the fields in the backentry, such as ep_state, ep_refcnt, ep_size and double linked list for LRU. We may be able to handle ep_state, ep_refcnt, and ep_size using some atomic operation (e.g., slapi_counter) to reduce the cache global lock.

But maintaining 3 slapi_counter in each entry could be also expensive. We need more investigation.


Metadata Update from @nhosoi:
- Issue set to the milestone: 1.4 backlog

7 years ago

Metadata Update from @firstyear:
- Issue assigned to firstyear

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: 1.4.5 (was: 1.4 backlog)
- Issue tagged with: Performance

3 years ago

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/1240

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)

3 years ago

Login to comment on this ticket.

Metadata