From mboxrd@z Thu Jan  1 00:00:00 1970
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: KADOTA Kyohei <lufia@me.com>
In-reply-to: <A1D8C0A6-BB79-42EB-9874-C3F4A8FCC1F6@9srv.net>
Date: Tue,  5 May 2015 23:47:31 +0900
Content-transfer-encoding: quoted-printable
Message-id: <919294DB-2559-46FB-9800-DB0FBDB63AF6@me.com>
References: <87C61423-7C13-4516-88B5-C2ABA7D32AA9@me.com>
	<A1D8C0A6-BB79-42EB-9874-C3F4A8FCC1F6@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil+venti performance question
Topicbox-Message-UUID: 4ef33a4c-ead9-11e9-9d60-3106f5b1d025

Thanks Anthony.

> I bet if you re-run the same test twice in a
> row, you=E2=80=99re going to see dramatically improved
> performance.

I try to re-run =E2=80=98iostats md5sum /386/9pcf=E2=80=99.
Read result is very fast.

first read result is 152KB/s.
second read result is 232MB/s.

> Your write performance in that test isn=E2=80=99t really
> relevant: they=E2=80=99re not hitting the file system at all.

I think to write 1GB data to filesystem:

	iostats dd -if /dev/zero -of output -ibs 1024k -obs 1024k -count =
1024

Write result of dd is 31MB/s.
But this test may just write to fossil. It may not write to venti.

> I=E2=80=99m not sure why you=E2=80=99d see a difference in a
> fossil+venti setup of a different size, but the
> partition size relationships, and the in-memory
> cache size relationships, are what=E2=80=99s mostly important.

My hardware has 2GB memory.
Plan 9 configurations are almost default. (except /dev/sdC0/bloom)
To increase memory size is difficult,
because memory size is determined by public QEMU/KVM service plan.

=E2=80=94
kadota=