-
Notifications
You must be signed in to change notification settings - Fork 272
Description
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/918
- Created at 2011-07-05 20:47:53 by sgallagh
- Closed as Fixed
- Assigned to sgallagh
- Associated bugzillas
SSSD has a cache update feature that can renew the cache prior to expiration to reduce the cache-miss penalty on oft-requested entries. We originally opted to leave it disabled by default (since it increases load slightly on the LDAP server).
However, I think the performance gains on the client side are well-worth the small load increase on the server side (which would still be much lower than the load without SSSD at all).
I propose that we should change the default value for {{{entry_cache_nowait_percentage}}} to be 50% (so entries would automatically refresh out-of-band when they were queried after half of their expiration time has passed).
Comments
Comment from dpal at 2011-07-07 14:57:30
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.1
Comment from sgallagh at 2011-08-26 23:01:38
Fields changed
milestone: SSSD 1.6.1 => SSSD 1.6.2
rhbz: =>
Comment from sgallagh at 2011-09-08 18:58:38
Fields changed
patch: 0 => 1
Comment from sgallagh at 2011-09-08 20:36:20
Fields changed
status: new => assigned
Comment from sgallagh at 2011-09-22 22:29:53
Fixed by:
- db2c71b (master)
- 77861bc (sssd-1-6)
resolution: => fixed
status: assigned => closed
Comment from sgallagh at 2012-01-30 21:54:08
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785898
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785898 785898]
Comment from sgallagh at 2017-02-24 14:57:32
Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.6.2