public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yohan <ytordjman@corp.free.fr>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
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 15:39:37 +0200	[thread overview]
Message-ID: <4A9FC719.9020104@corp.free.fr> (raw)
In-Reply-To: <1251982884.18338.9.camel@heimdal.trondhjem.org>


>>> I did only:
>>>
>>> --- linux-2.6.27.21/include/linux/sunrpc/auth.h	2009-03-23 23:04:09.000000000 +0100
>>> +++ linux-2.6.27.21/include/linux/sunrpc/auth.h	2009-05-19 16:02:35.000000000 +0200
>>> @@ -62,8 +62,12 @@ 
>>>   */
>>> - #define RPC_CREDCACHE_HASHBITS	4
>>> + #define RPC_CREDCACHE_HASHBITS	12
>>>
>>>
>>> And i test it in prod since sunday: i only have 36% of one core used by 
>>> system
>>> versus more than 3 cores used by system in another server that did a 
>>> drop_caches at morning...
>>>       
>> OK, but it's still pretty bad.  Let's tell the NFS guys.
>>
>> In http://bugzilla.kernel.org/show_bug.cgi?id=14024 we appear to have a
>> major meltdown caused by the linear search in
>> rpcauth_lookup_credcache() with Yohan's workload.
>>     
> OK. Could we please have some more details about the actual workload involved here?
>   
I add a new server CPU graph and 60s readprofile on the bugzilla

> 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.


  reply	other threads:[~2009-09-03 13:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 14:23 VM issue causing high CPU loads 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 [this message]
2009-09-03 14:02             ` Trond Myklebust
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=4A9FC719.9020104@corp.free.fr \
    --to=ytordjman@corp.free.fr \
    --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=trond.myklebust@fys.uio.no \
    /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