All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gergely Gábor" <elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: some notes on a memory leak
Date: Thu, 14 Feb 2008 01:02:58 +0100	[thread overview]
Message-ID: <20080214010258.76494d68@vosztok> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2208 bytes --]

Hello Ryusuke, and other nilfs developers, and users!

I have left my computer working, testing nilfs. I have found that after a log period of time, most of the memory in the computer vas allocated as cache (according to vmstat) and even aftel killing all processes that held files open, the amount (~430 megabytes) did not decrease significantly. I have unmounted the filesystem, and most cache was freed up, and after remounting nilfs, the system was fast as lightning again (the module was not needed to be removed to reclaim the memory). This leads to the assumption, that some data is left cached, even when not in use. To reproduce this behaviour, I simply started "vmstat 1", and rtorrent, started a download, and watched the cache consumption climb. after exiting rtorrent, most of the cache is not reclaimed, not even after a long period of time. (i understand, that leaving blocks in the cache is preferable for a log structured fs, as that reduces seeks necessary for reading, but possibly some aging mechanism, and/or a maximum cache size option would be a good idea to implement in the future, if not yet done)

Apart from this minor issue, the fs is working fine. i feel that (but this is very subjective, only based on my perception) the current rate of this leakage is far smaller that the rate i experienced with the patched version of testing-8. (than the system went unusable after a few minutes, as all mem was consumed, not it took more than 4 hours, as i wrote a letter with fairly much free mem before leaving home with the machine running.)

Sorry for flooding the mail list with my self-contradictory status reports.

Please tell me, where can i read about the architecture of nilfs2 in greater detail, other than the code? (i'm willing to understand the code as well, but i'd need some guidance, where to start. I'd be the most happy if i could provide some more useful help rather than constant "complaining") has many things changed since nilfs1? (i have found papers about that on the project homepage)

Yours sincerely: Gergely Gábor
-- 
Gergely Gábor <elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

* random fortune:
Rome wasn't burnt in a day.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users

             reply	other threads:[~2008-02-14  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  0:02 Gergely Gábor [this message]
2008-02-15  3:18 ` some notes on a memory leak Ryusuke Konishi
2008-02-15  6:07 ` Ryusuke Konishi
     [not found]   ` <20080215.150709.13051610.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-02-15  6:42     ` Ryusuke Konishi
2008-02-16 22:13     ` Gergely Gábor

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=20080214010258.76494d68@vosztok \
    --to=elentirmo.gilgalad-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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.