From: Jiri Horky <jiri.horky@cesnet.cz>
To: Zhang Taile <zhangtl@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: memory leak bug? when do write with verify
Date: Wed, 14 Sep 2011 11:56:23 +0200 [thread overview]
Message-ID: <4E707A47.1060002@cesnet.cz> (raw)
In-Reply-To: <CADson1wi5=W-WDbDGy1j2T4FZD_2yoGGzOG8Af7GKKppiY7Lrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hi,
this sounds like the problem addressed by this thread [1]. Have you
tried to use the latest (trunk) version that includes the mentioned patch?
Jiri Horky
[1] http://www.spinics.net/lists/fio/msg00843.html
On 09/14/2011 11:53 AM, Zhang Taile wrote:
> HI
> When I do RandWrite with verify, fio will use a lot of memory. The fio
> will increase memory about 10MB in every second. And, the system will
> become very slow, after fio start to use swap partition.
>
> For example, if use fio with following configuration,
> [rand-write]
> rw=randwrite
> numjobs=32
> loops=10
> thread=1
> filename=/dev/sdb
> verify=md5
> verify_interval=4k
>
> after minutes, top will Like this :
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 3749 root 15 0 2672m 1.5g 304m S 169.4 40.4 4:10.04 fio
>
>
> If remove the verify from the configuration, there will be no the
> memory problem.
>
> I guess it is a memory leak problem?
>
>
> Thanks!
> --
> Taile
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6917 bytes --]
next prev parent reply other threads:[~2011-09-14 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADson1wk9astwdroeAtPXb4A3+yrAcDcCXaEPvEGJPhM4TBfqQ@mail.gmail.com>
2011-09-14 9:53 ` memory leak bug? when do write with verify Zhang Taile
2011-09-14 9:56 ` Jiri Horky [this message]
2011-09-14 13:13 ` Zhang Taile
2011-09-14 17:39 ` Jens Axboe
2011-09-15 2:49 ` Zhang Taile
2011-09-15 7:24 ` Jens Axboe
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=4E707A47.1060002@cesnet.cz \
--to=jiri.horky@cesnet.cz \
--cc=fio@vger.kernel.org \
--cc=zhangtl@gmail.com \
/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.