All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgios Tsalikis <georgios@tsalikis.net>
To: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 extremely slow at deleting.
Date: Wed, 27 Jul 2016 21:39:55 +0300	[thread overview]
Message-ID: <nnav5v$rgh$1@ger.gmane.org> (raw)
In-Reply-To: <0aa0ad49-a6a7-4d53-8a91-aa78821156c2@intersafeit.com>

Here is my disappointing data :p

# measurefs.reiser4 -p /dev/sdc3
measurefs.reiser4 1.1.0
Format release: 4.0.1
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by 
reiser4progs/COPYING.

Default profile:
create:          "ccreg40"         (id:0x4 type:0x0)    [Regular file 
plugin for creat(2)]
key:             "key_large"       (id:0x1 type:0xb)    [Key plugin]
node:            "node40"          (id:0x0 type:0x2)    [Node plugin]
compress:        "lzo1"            (id:0x0 type:0xc) [Compression plugin]
compressMode:    "conv"            (id:0x4 type:0xd) [Compression Mode 
plugin]
cluster:         "64K"             (id:0x0 type:0x10)    [Cluster plugin]
hash:            "r5_hash"         (id:0x1 type:0x3)    [Directory entry 
hash plugin]
fibration:       "ext_1_fibre"     (id:0x2 type:0x4)    [Key fibration 
plugin]
formatting:      "smart"           (id:0x2 type:0x5)    [File body 
formatting plugin]

(actually i formatted it with node41 but it doesn't appear so)

# ls -l resstick.dd
-rw-r--r-- 1 root root 22007840768 Ιούλ 26 15:03 resstick.dd
# time rm resstick.dd

real    21m43.005s
user    0m0.000s
sys    5m2.132s

If this is not problematic then what is? It is a single deletion!!


On 27/07/2016 09:15 μμ, Morgan Smith wrote:
> Was the file system created using the reg40 plugin or ccreg40 for on the
> fly compression?
>
> It seems to me I had this issue when using ccreg40 for on the fly
> compression. I wrote a similar request for help some years ago and I
> believe the answer was to not use compression. IIRC it's not an issue
> with the compression itself rather the handling of allocated space for
> it and the shuffling that is done when releasing resources. I was unable
> to quickly find my old email to the list to confirm :(
>
> On 07/27/2016 11:51 AM, Georgios Tsalikis wrote:
>> It is almost always like this. For example a directory with 2.5GB of
>> large files takes about 2 minutes. Right now i am deleting a large
>> directory with small files, I didn't keep the numbers before running,
>> but they are many directories with source code. Could it be
>> fragmentation? And how could I mitigate it? Thanks
>>
>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe
>> reiserfs-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-07-27 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 17:51 Reiser4 extremely slow at deleting Georgios Tsalikis
2016-07-27 18:15 ` Morgan Smith
2016-07-27 18:39   ` Georgios Tsalikis [this message]
2016-07-27 19:24     ` Edward Shishkin
2016-07-27 20:40       ` Georgios Tsalikis

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='nnav5v$rgh$1@ger.gmane.org' \
    --to=georgios@tsalikis.net \
    --cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.