public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Best file system for portage tree?
Date: Sat, 10 Mar 2012 14:30:15 +0100	[thread overview]
Message-ID: <20120310143015.6d507af3@weird.wonkology.org> (raw)

Hi there!

Is there an advantage in putting the portage tree on an extra partition?

Currently, I'm using reiserfs, because I read that it is efficient when
using many small files. On the other hand I also heard that it tends to
get slower with every emerge --sync.

Space is no longer an argument in these days, at least for my desktop
machine. But I would like to optimize for speed -- emerge -DputnVj
@world takes quite a while to calculate, I assume this is because so many
ebuild files have to be accessed.

Any tips on this? Does it make sense to use a special file system just
for the portage tree? What would be best? Would it help to re-create this
file system from time to time in case it gets slower with every sync? Or
wouldn't I notice a difference if I just used a big ext4 partition for
all portage related stuff?

Anyone using a compressed RAM file system for that? :)

	Wonko



             reply	other threads:[~2012-03-10 13:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 13:30 Alex Schuster [this message]
2012-03-10 14:39 ` [gentoo-user] Best file system for portage tree? Dale
2012-03-10 14:40 ` Florian Philipp
2012-03-10 15:09 ` Pandu Poluan
2012-03-10 15:14   ` Pandu Poluan
2012-03-10 17:20   ` Bryan Gardiner
2012-03-10 15:35 ` Neil Bothwick
2012-03-10 18:36   ` YoYo Siska
2012-03-10 19:38     ` Neil Bothwick
2012-03-11 22:42     ` Alex Schuster
2012-03-12  9:15     ` José Romildo Malaquias
2012-03-12  9:23       ` Alex Schuster
2012-03-13 12:30         ` YoYo Siska

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=20120310143015.6d507af3@weird.wonkology.org \
    --to=wonko@wonkology.org \
    --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