From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: "James A. Robinson" Date: Wed, 2 Nov 2016 18:44:37 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114e5840e287ef054055d577 Subject: Re: [9fans] Fossil+Venti system memory requirements to be aware of? Topicbox-Message-UUID: a8b414de-ead9-11e9-9d60-3106f5b1d025 --001a114e5840e287ef054055d577 Content-Type: text/plain; charset=UTF-8 On Wed, Oct 19, 2016 at 9:47 AM Steven Stallion wrote: > In short, start small and grow as needed. For reference, when I ran > Coraid's fs based on 64-bit Ken's (WORM only, no dedupe) in RWC > (based on the main fs in Athens). Over the course of a few years > the entire WORM grew to around 35GB. This was for a couple dozen > people working full time. I believe I had the LUN configured to > something rather large at the time - around 12TB. All wasted space. Hi, So if you were setting up a new filesystem for the same group, and were using venti, would you be using the default 500 mb arena size (meaning 70+ arenas), or would you be sizing them at a larger size, like 1 gb, 2 gb, etc? The "setting up venti" page indicates that multiple small disks help with performance on venti due to using more indexes, but I can't tell if that translates to more partitions (e.g., 1 RAID 1+0 disk split into multiple smaller partitions, and divvied up into isectX and arenaX drives). I guess it probably comes down to how well (or poorly) the underlying disk array performs at random read/write ops. I see that AWS S3 allows for up to 5 gb in a single PUT, or 5 tb using multipart streams, and am thinking that using 1 to 5 gb arenas might make sense as a more modern "sized for for easy offline backup" default. Jim --001a114e5840e287ef054055d577 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Wed, Oct 19, 2016 at 9:47 AM Steven Stal= lion <sstallion@gmail.com>= wrote:
> In short, start small and grow as needed. For refere= nce, when I ran
> Coraid's fs based on 64-bit Ken's (W= ORM only, no dedupe) in RWC
> (based on the main fs in Athens)= . Over the course of a few years
> the entire WORM grew to aro= und 35GB. This was for a couple dozen
> people working full ti= me. I believe I had the LUN configured to
> something rather l= arge at the time - around 12TB. All wasted space.

Hi,

So if you were setting up a new filesyst= em for the same group, and
were using venti, would you be using t= he default 500 mb arena size
(meaning 70+ arenas), or would you b= e sizing them at a larger size,
like 1 gb, 2 gb, etc?
<= br>
The "setting up venti" page indicates that multiple= small disks
help with performance on venti due to using more ind= exes, but I
can't tell if that translates to more partitions = (e.g., 1 RAID 1+0
disk split into multiple smaller partitions, an= d divvied up into
isectX and arenaX drives).=C2=A0 I guess it pro= bably comes down to
how well (or poorly) the underlying disk arra= y performs at random
read/write ops.

I s= ee that AWS S3 allows for up to 5 gb in a single PUT, or 5 tb
usi= ng multipart streams, and am thinking that using 1 to 5 gb
arenas= might make sense as a more modern "sized for for easy
offli= ne backup" default.

Jim

<= /div>
--001a114e5840e287ef054055d577--