All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: linux-nfs@vger.kernel.org
Subject: Temporary hangs when using locking with apache+nfsv4
Date: Mon, 03 Mar 2014 06:47:52 +0100	[thread overview]
Message-ID: <53141788.9030209@conversis.de> (raw)

Hi,
I'm experimenting with using NFSv4 as storage for web servers and while 
regular file access seems to work fine as soon as I bring flock() into 
play things become more problematic.
I've create a tiny test php script that basically opens a file, locks it 
using flock(), writes that fact into a log file (on a local filesystem), 
performs a usleep(1000), writes into the log that it is about to unlock 
the file and finally unlocks it.
I invoke that script using ab with a concurrency of 20 for a few 
thousand requests.

The result is that while 99% of the request respond quickly a few 
request seem to hang for up to 30 seconds. According to the log file 
they must eventually succeed since I see all expected entries and the 
locking seems to work as well since all entries are in the expected order.

Is it expected that these long delays happen? When I comment the locking 
function out these hangs disappear.
Are there some knobs to tune NFS and make it behave better in these 
situations?

Regards,
   Dennis

             reply	other threads:[~2014-03-03  6:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  5:47 Dennis Jacobfeuerborn [this message]
2014-03-03 15:43 ` Temporary hangs when using locking with apache+nfsv4 Jeff Layton
2014-03-03 15:46   ` Trond Myklebust
2014-03-03 16:41     ` Jeff Layton
2014-03-03 18:22       ` Trond Myklebust
2014-03-03 18:34         ` Jeff Layton
2014-03-03 19:02           ` Trond Myklebust
2014-03-03 22:41             ` Jeff Layton
2014-03-03 20:41       ` J. Bruce Fields
2014-03-03 22:29         ` Jeff Layton
2014-03-03 22:35           ` J. Bruce Fields
2014-03-03 23:03   ` Dennis Jacobfeuerborn

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=53141788.9030209@conversis.de \
    --to=dennisml@conversis.de \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.