From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Yohan <ytordjman@corp.free.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Neil Brown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
mikevs@xs4all.net
Subject: Re: VM issue causing high CPU loads
Date: Thu, 03 Sep 2009 10:02:06 -0400 [thread overview]
Message-ID: <1251986526.18338.29.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <4A9FC719.9020104@corp.free.fr>
On Thu, 2009-09-03 at 15:39 +0200, Yohan wrote:
> > As far as I can see, there is no RPCSEC_GSS involved, so credentials
> > should never expire. They will be reused as long as processes aren't
> > switching between thousands and thousands of different combinations of
> > uid, gid and groups.
> My servers are imap servers.
> Foreach user (~15 million) it have a specific uid over ~10 nfs netapp
> storage.
OK, so 16 hash buckets are likely to be filled with ~10^6 entries each.
I can see that might be a performance issue...
So afaics, you did try adjusting the hashtable size. How much larger
does it have to be before you start to get acceptable performance? If it
solves your problem we could make hash table sizes adjustable via a
module parameter, for instance.
Cheers
Trond
next prev parent reply other threads:[~2009-09-03 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 14:23 Yohan
2009-08-24 23:21 ` Andrew Morton
2009-08-26 11:08 ` Mel Gorman
2009-08-26 11:55 ` Yohan
2009-08-26 11:53 ` Yohan
2009-08-27 8:39 ` Yohan
2009-08-31 20:39 ` Yohan
2009-09-03 0:06 ` Andrew Morton
2009-09-03 13:01 ` Trond Myklebust
2009-09-03 13:39 ` Yohan
2009-09-03 14:02 ` Trond Myklebust [this message]
2009-09-03 14:08 ` Yohan
2009-09-03 14:35 ` sunrpc: dynamically allocate credcache hashtables [was: Re: VM issue causing high CPU loads] Miquel van Smoorenburg
2009-09-03 20:05 ` VM issue causing high CPU loads Simon Kirby
2009-09-03 20:49 ` Trond Myklebust
2009-09-03 22:22 ` Simon Kirby
2009-09-04 12:31 ` Trond Myklebust
2009-09-03 21:21 ` Muntz, Daniel
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=1251986526.18338.29.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=neilb@suse.de \
--cc=ytordjman@corp.free.fr \
/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: link
Be 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
all inboxes | Powered by JetHome®