From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: deleting 2TB lots of files with delaylog: sync helps?
Date: Thu, 2 Sep 2010 04:15:47 +0200 [thread overview]
Message-ID: <201009020415.47780@zmi.at> (raw)
In-Reply-To: <20100902011744.GS705@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1451 bytes --]
On Donnerstag, 2. September 2010 Dave Chinner wrote:
> -> free block
Is the SSD-needed "trim" belonging into here?
> In contrast, XFS CPU consumption increases per-operation in a
> predictable fashion - O(log n) where n is the number of directory
> entries. e.g for 4k directory blocks it increases by ~2x from 100k
> entries to 1m entries, and another 2x from 1M entries to 10M entries
> and so on, but the result is that the IO patterns are rarely enough
> to cause operations to become seek bound.
Now I understand, thanks again for that great explanation.
> > Maybe there should be an extra SSE4 assembler instruction "rm on
> > XFS" so we can delete files faster? ;-)
>
> You'd need an entire ASIC, not an instruction ;)
Time to invent the "XFS rm co-processor". Should be multi-core so it
scales better. Maybe someone writes a graphics cards plugin for XFS?
Then we'd see an increase of servers with fast GFX cards "because we
need to delete files quickly". And at times no users are deleting files,
the admins can play Doom on the servers. ;-)
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-02 2:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 23:30 deleting 2TB lots of files with delaylog: sync helps? Michael Monnerie
2010-09-01 0:06 ` Dave Chinner
2010-09-01 0:22 ` Michael Monnerie
2010-09-01 3:19 ` Dave Chinner
2010-09-01 4:42 ` Stan Hoeppner
2010-09-01 6:44 ` Dave Chinner
2010-09-02 5:37 ` Stan Hoeppner
2010-09-02 7:01 ` Dave Chinner
2010-09-02 8:41 ` Stan Hoeppner
2010-09-02 11:29 ` Dave Chinner
2010-09-02 14:57 ` Stan Hoeppner
2010-09-01 3:01 ` Stan Hoeppner
2010-09-01 3:41 ` Dave Chinner
2010-09-01 7:45 ` Michael Monnerie
2010-09-02 1:17 ` Dave Chinner
2010-09-02 2:15 ` Michael Monnerie [this message]
2010-09-02 7:51 ` Stan Hoeppner
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=201009020415.47780@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox