public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Normal disk speed?
Date: Fri, 01 Oct 2010 10:42:38 +0200	[thread overview]
Message-ID: <4CA59EFE.2020403@f_philipp.fastmail.net> (raw)
In-Reply-To: <AANLkTino4UGfa+9u_tSU3jj4Y-hpTwRRxt26NNhZvZcB@mail.gmail.com>

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

Am 01.10.2010 03:12, schrieb Adam Carter:
>     Your harddisk seeks, everything is slow.
> 
> So does that then mean that my options are;
> 1. Defragment, so there is less seeking
> 2. Get an SSD
> 
> Since 2 is too expensive for a decent size drive, is there anything i
> can do about 1 without a backup and restore operation? Or will the
> fragmentation be very small on reiser3 anyway (i mount with notail) so I
> should just accept things as they are.

To prevent fragmentation, try to always keep a decent amount of free
space on each partition. That way, the FS driver can allocate space for
new files without too much fragmentation (a fragment every 2 MB or so
doesn't really hurt performance).

If you had enough free space on your partition when you created the
mp3-files there, I don't think fragmentation is an issue here. The files
likely never grew in size which would cause fragmentation.

Of course, the situation changes again when the free space on your file
system was already heavily fragmented even if there was enough of it. It
all depends on your usage pattern of that disk to make an educated guess
if that is true.

The good thing about hard disks is that you can usually hear whether
they are seeking or reading sequentially. If you hear a lot of seeking
on sequential operations, it is time to reformat the partition or at
least erase and recreate the affected files.

Hope this helps,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2010-10-01  8:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 10:58 [gentoo-user] Normal disk speed? Adam Carter
2010-09-30 13:10 ` Florian Philipp
2010-09-30 16:00   ` Peter Humphrey
2010-09-30 16:12     ` [gentoo-user] " Nikos Chantziaras
2010-09-30 16:50     ` [gentoo-user] " Florian Philipp
2010-09-30 21:43       ` Peter Humphrey
2010-09-30 13:26 ` [gentoo-user] " James
2010-09-30 16:53 ` [gentoo-user] " Volker Armin Hemmann
2010-10-01  1:12   ` Adam Carter
2010-10-01  4:41     ` Volker Armin Hemmann
2010-10-01  8:42     ` Florian Philipp [this message]
2010-10-01 16:23       ` Volker Armin Hemmann
2010-10-02  2:11         ` Adam Carter
2010-10-02 11:54         ` Florian Philipp
2010-10-02 12:11           ` Volker Armin Hemmann
2010-10-02 12:44             ` Florian Philipp
2010-10-02 15:06               ` Florian Philipp
2010-10-01  9:05     ` Daniel Troeder
2010-10-01 14:40       ` [gentoo-user] " James
2010-10-02 17:29         ` Daniel Troeder
2010-10-03  0:13           ` James
2010-10-06  8:04             ` Adam Carter
2010-10-06 18:52               ` Daniel Troeder
2010-10-06 22:59                 ` Adam Carter
2010-10-07  9:33                   ` Daniel Troeder
2010-10-18 10:03                     ` Adam Carter

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=4CA59EFE.2020403@f_philipp.fastmail.net \
    --to=lists@f_philipp.fastmail.net \
    --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