All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Marcin Krol <mrkafk@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inotify limits - thousands (tens of thousands?) of watches
Date: Wed, 20 May 2009 12:04:23 +0200	[thread overview]
Message-ID: <20090520100423.GA3695@traven> (raw)
In-Reply-To: <4A13CCE1.5000106@gmail.com>

El Wed, May 20, 2009 at 11:26:57AM +0200 Marcin Krol ha dit:

> First, apols for using up bandwidth, but I honestly found no other place  
> where I can ask about this (and get meaningful reply).
>
> I'm not a kernel programmer, but I want to develop a program that would  
> watch modifications in *all* user directories on a busy server using  
> inotify.
>
> This is for high-availability purposes - events would be collected and  
> once every several minutes changed dirs would be rsync'ed to failover  
> server or smth like that would be done.
>
> As inotify watches particular directory and not its subdirs, I would  
> have to watch all directories.
>
> This means I would have to create thousands or even tens of thousands of  
> inotify watches.
>
> So my questions are:
>
> 1. is it safe? that is, will it not lock the kernel up, or cause  
> excessive memory consumption?
>
> 2. is it economic in terms of CPU time and RAM? I have no idea how to  
> even measure such a thing happening in the kernel..

i can't answer your question whether inotify scales or not, but maybe
DRBD (http://en.wikipedia.org/wiki/DRBD) could be an alternative
approach for your problem

-- 
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

    Me lo contaron y lo olvidé, lo vi y lo entendí, lo hice y lo aprendí
                              (Confucio)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2009-05-20 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  9:26 inotify limits - thousands (tens of thousands?) of watches Marcin Krol
2009-05-20 10:04 ` Matthias Kaehlcke [this message]
2009-05-20 10:12 ` Tvrtko Ursulin
2009-05-20 11:22 ` Martin Steigerwald
2009-05-20 12:16   ` Marcin Krol
2009-05-20 12:48     ` Martin Steigerwald
2009-05-20 12:58     ` Martin Steigerwald
2009-05-20 13:58 ` hooanon05

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=20090520100423.GA3695@traven \
    --to=matthias@kaehlcke.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrkafk@gmail.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: 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.