public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nick at sqrt dot co dot uk" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug nscd/1204] New: nscd cannot extend memory heap sizes Date: Wed, 17 Aug 2005 21:24:00 -0000 [thread overview] Message-ID: <20050817212410.1204.nick@sqrt.co.uk> (raw) The change in nscd to use mmap for memory allocation of caches presents a problem in that once the cache is full, mempool_alloc cannot extend the size of the cache because 'mremap' will always fail. 4279: no more memory for database 'group' $ nscd -g shows: 216064 total data pool size 214664 used data pool size 7 memory allocations failed The problem is that for a system with large group memberships (i.e. several thousand users), which are held in LDAP databases, as pool sizes cannot increase, the result is poor performance, with commands such as a simple 'ls' taking 10-20 seconds to complete. The group lookup cannot be cached because there is no further space to hold the data. Certainly it is possible to work around this problem by increasing 'suggested-size' from say 211 to 10007, but clearly the 'mremap' is going to fail in any case. Can we not use malloc and realloc instead ? -- Summary: nscd cannot extend memory heap sizes Product: glibc Version: 2.3.5 Status: NEW Severity: normal Priority: P2 Component: nscd AssignedTo: drepper at redhat dot com ReportedBy: nick at sqrt dot co dot uk CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://sources.redhat.com/bugzilla/show_bug.cgi?id=1204 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-08-17 21:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-17 21:24 nick at sqrt dot co dot uk [this message] 2005-08-24 1:17 ` [Bug nscd/1204] " drepper at redhat dot com 2006-05-03 5:57 ` twb0 at lymenet dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050817212410.1204.nick@sqrt.co.uk \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).