#48831 dncache is not tuned as part of autosizing and autotuning of caches.
Closed: wontfix 6 years ago Opened 7 years ago by firstyear.

the dncache is not tuned as part of automatic cache tuning or sizing. This should be fixed so that memory limits can be respected properly, and we have a complete autotuning function.


Setting the milestone to 1.3.6.

William, please feel free to reset it if you think differently.

Thanks!

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

7 years ago

Metadata Update from @firstyear:
- Issue assigned to firstyear

7 years ago

Metadata Update from @firstyear:
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)

7 years ago
[05/Sep/2017:14:03:36.111454695 +1000] - NOTICE - ldbm_back_start - found 12037612k physical memory
[05/Sep/2017:14:03:36.129604876 +1000] - NOTICE - ldbm_back_start - found 7460844k available
[05/Sep/2017:14:03:36.145962676 +1000] - NOTICE - ldbm_back_start - cache autosizing: db cache: 300940k
[05/Sep/2017:14:03:36.158918892 +1000] - NOTICE - ldbm_back_start - cache autosizing: userRoot entry cache (1 total): 851968k
[05/Sep/2017:14:03:36.174797796 +1000] - NOTICE - ldbm_back_start - cache autosizing: userRoot dn cache (1 total): 131072k
[05/Sep/2017:14:03:36.192228262 +1000] - NOTICE - ldbm_back_start - total cache size: 1991360757 B; 

0001-Ticket-48831-Autotune-dncache-with-entry-cache.patch

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to None

6 years ago

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to review (was: None)

6 years ago
200 +        if (dncache_size == 0 || dncache_size == MINCACHESIZE || li->li_cache_autosize > 0) {
201 +            slapi_log_err(SLAPI_LOG_NOTICE, "ldbm_back_start", "cache autosizing: %s dn cache (%lu total): %luk\n", inst->inst_name, backend_count, dn_size / 1024);
202 +            cache_set_max_entries(&(inst->inst_dncache), -1);
203 +            cache_set_max_size(&(inst->inst_dncache), li->li_dncache_autosize_ec, CACHE_TYPE_DN);
204 +        }

It looks like even if you set a specific dn cache size it is ignored if auto-tuning is enabled. Is that the desired behavior? I thought if you set your own value then autotuning is not applied.

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

6 years ago

commit e9c7e474a559d09744d793254cebfe55967ad1cc
To ssh://git@pagure.io/389-ds-base.git
f63949d..aa57d4b master -> master

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 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/1891

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 (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata