public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Hampicke <mgehampicke@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fast file system for cache directory with lot's of files
Date: Mon, 13 Aug 2012 16:53:25 +0200	[thread overview]
Message-ID: <CADPZhupfd9L1_KwhU9Tg9sEDBTDLNzhBsWZc2txqT4_mmoS8vQ@mail.gmail.com> (raw)
In-Reply-To: <5029114E.8070402@admin-box.com>

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

2012/8/13 Daniel Troeder <daniel@admin-box.com>

> On 13.08.2012 15:16, Michael Hampicke wrote:
> > - about 20GB
> > - 100.000 directories
> > - about 2 million files
> >
> > The system has 2x Intel Xon Quad-cores (Nehalem), 16GB of RAM and two
> > 10.000rpm hard drives running a RAID1.
> 1st thought: switch to SSDs
> 2nd thought: maybe lots of writes? -> get a SSD for the fs metadata
> 3rd thought: purging old files with "find"? your cache system should
> have some kind of DB that holds that information.
>
>
1: SSDs are not possible atm. The machine is in a data center abroad.
2: Writes are not that much of a problem at this time.
3: Well, it's a 3rd party application that - in theory - should take care
of removing old files. Sadly, it does not work as it's supposed to be,
While time passes the number of orphans grow :(

[-- Attachment #2: Type: text/html, Size: 1210 bytes --]

  reply	other threads:[~2012-08-13 15:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:16 [gentoo-user] Fast file system for cache directory with lot's of files Michael Hampicke
2012-08-13 13:22 ` Nilesh Govindrajan
2012-08-13 13:54   ` Michael Hampicke
2012-08-13 14:19     ` Pandu Poluan
2012-08-13 14:42       ` Michael Hampicke
2012-08-13 14:52         ` Michael Mol
2012-08-13 15:26           ` Michael Hampicke
2012-08-13 15:52             ` Michael Mol
2012-08-13 17:14           ` Florian Philipp
2012-08-13 18:18             ` Michael Hampicke
2012-08-14 14:00               ` Florian Philipp
2012-08-14 17:42                 ` Michael Hampicke
2012-08-13 14:40     ` Dale
2012-08-13 14:58       ` Michael Hampicke
2012-08-13 15:20         ` Nilesh Govindrajan
2012-08-13 14:38 ` Daniel Troeder
2012-08-13 14:53   ` Michael Hampicke [this message]
2012-08-14  8:21     ` Daniel Troeder
2012-08-14  9:46       ` Neil Bothwick
2012-08-14 13:00         ` Florian Philipp
2012-08-14 13:54         ` Daniel Troeder
2012-08-14 15:09           ` Florian Philipp
2012-08-14 15:33             ` Florian Philipp
2012-08-16 16:54           ` Neil Bothwick
2012-08-14 17:45       ` Michael Hampicke
2012-08-13 20:13 ` Paul Hartman
2012-08-13 20:41   ` Volker Armin Hemmann
2012-08-14  2:07   ` Adam Carter
2012-08-14 16:36     ` Helmut Jarausch
2012-08-14 17:05       ` Pandu Poluan
2012-08-14 17:21         ` Jason Weisberger
2012-08-14 17:42           ` Volker Armin Hemmann
2012-08-14 17:50             ` Michael Hampicke
2012-08-14 19:55               ` Alecks Gates
2012-08-14 20:17                 ` Michael Mol
2012-08-14 20:57                   ` Alecks Gates
2012-08-14 17:48           ` Michael Hampicke
2012-08-14 17:42         ` Volker Armin Hemmann
2012-08-14 19:39         ` Paul Hartman
2012-08-15  7:31       ` Bill Kenworthy
2012-08-15  8:13         ` Bill Kenworthy

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=CADPZhupfd9L1_KwhU9Tg9sEDBTDLNzhBsWZc2txqT4_mmoS8vQ@mail.gmail.com \
    --to=mgehampicke@gmail.com \
    --cc=gentoo-user@lists.gentoo.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