Bug #6294
closed
Slapd uses 259888kB swap
Added by Dennis Cabooter about 9 years ago. Updated about 7 years ago.
Description
Slapd uses 259888kB since Rudder 3.0. The total amount of memory in my Rudder server is 4G.
Updated by François ARMAND about 9 years ago
It may be due to the optimisation in OpenLDAP we made. OpenLDAP has a multi-layered architecture, and we have cache at different level. We observed that given the usage profile of openLDAP in Rudder, all data can easily be put in the first layer cache (so, big speed upgrade). So perhaps what you see is Linux learning that deeper level of cache and data are never accessed, and puts them in swap.
Is it a problem to have that in swap ? In http://www.rudder-project.org/redmine/issues/6287#note-4, you seems to think that no i/o are consumed for it, do you see other problems ?
Updated by Dennis Cabooter about 9 years ago
I don't see any problems with it right now. I just wanted to bring this to your attention, because I can't determine the impact.
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.2 to 3.0.3
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.3 to 3.0.4
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.4 to 3.0.5
Updated by Benoît PECCATTE almost 9 years ago
- Category set to Performance and scalability
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.0.5 to 3.0.6
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.0.6 to 3.0.7
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.0.7 to 3.0.8
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.8 to 3.0.9
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.9 to 3.0.10
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.10 to 3.0.11
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.11 to 3.0.12
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.12 to 3.0.13
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.0.13 to 3.0.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.0.14 to 3.0.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.0.15 to 3.0.16
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.0.16 to 3.0.17
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.0.17 to 302
Updated by Alexis Mousset almost 8 years ago
- Target version changed from 302 to 3.1.12
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Jonathan CLARKE about 7 years ago
- Status changed from New to Rejected
This issue doesn't seem to have any negative impact, and Rudder >= 4.1 uses a completely different LDAP backend (LMDB). Therefore, I'm closing this bug - if anyone ever sees a negative impact because of this, please reopen this issue.