From: Dave Chinner <david@fromorbit.com>
To: David Shaw <dshaw@jabberwocky.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Quota performance hit?
Date: Wed, 3 Jan 2018 17:43:43 +1100 [thread overview]
Message-ID: <20180103064342.GE30682@dastard> (raw)
In-Reply-To: <3DED9052-77EA-4405-BE33-89807AEE23EC@jabberwocky.com>
On Wed, Jan 03, 2018 at 12:02:13AM -0500, David Shaw wrote:
> Hello,
>
> I wonder if anyone could point me towards any numbers on how much
> of a performance penalty project quotas incur on a write-heavy
> filesystem. The idea being discussed here is putting a project
> quota on the /var/log directory (so pretty write-heavy)
/var/log is definitely a "mostly write" directory, but I wouldn't
ever classify it as "write heavy".
Unless you are trying to perform thousands of concurrent writes
and/or log file creation/removal operations every second to
/var/log, then putting a project quota on that directory is not
going to cause you any sort of noticable problem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-01-03 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 5:02 Quota performance hit? David Shaw
2018-01-03 6:43 ` Dave Chinner [this message]
2018-01-03 13:32 ` David Shaw
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=20180103064342.GE30682@dastard \
--to=david@fromorbit.com \
--cc=dshaw@jabberwocky.com \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox