From: Sergey Zhilkin <szhilkin@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil+venti performance question
Date: Tue, 5 May 2015 17:29:46 +0300 [thread overview]
Message-ID: <CAOFTvP+YO-DeOq7Y=iO__MzBELXczsusExkUXcQLykQ-4EcBjg@mail.gmail.com> (raw)
In-Reply-To: <CANUoZoERAwWAMxLYGiAGOihHBwPAq07XyKmiTyCg2tmgvaO44Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Hello!
imho placing fossil, venti, isect, bloom and swap on single drive is bad
idea.
As written in in http://plan9.bell-labs.com/sys/doc/venti/venti.html - "The
prototype Venti server is implemented for the Plan 9 operating system in
about 10,000 lines of C. The server runs on a dedicated dual 550Mhz Pentium
III processor system with 2 Gbyte of memory and is accessed over a 100Mbs
Ethernet network. The data log is stored on a 500 Gbyte MaxTronic IDE Raid
5 Array and the index resides on a string of 8 Seagate Cheetah 18XL 9 Gbyte
SCSI drives."
God ide is to store isect on multiple SSD drives :) to speed up search.
My small installation - 80Gb (PATA) 9fat, fossil, swap + 40Gb isect, bloom
drive (PATA) + 1Tb SATA as arenas. No RAID.
2015-05-04 21:51 GMT+03:00 David du Colombier <0intro@gmail.com>:
> I'm experiencing the same issue as well.
>
> When I launch vacfs on the same machine as Venti,
> reading is very slow. When I launch vacfs on another
> Plan 9 or Unix machine, reading is fast.
>
> I've just made some measurements when reading a file:
>
> Vacfs running on the same machine as Venti: 151 KB/s
> Vacfs running on another machine: 5131 KB/s
>
> --
> David du Colombier
>
>
--
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey
[-- Attachment #2: Type: text/html, Size: 2324 bytes --]
next prev parent reply other threads:[~2015-05-05 14:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:32 KADOTA Kyohei
2015-05-04 16:10 ` Anthony Sorace
2015-05-04 18:11 ` Aram Hăvărneanu
2015-05-04 18:51 ` David du Colombier
2015-05-05 14:29 ` Sergey Zhilkin [this message]
2015-05-05 15:05 ` Charles Forsyth
2015-05-05 15:38 ` David du Colombier
2015-05-05 22:23 ` Charles Forsyth
2015-05-05 22:29 ` cinap_lenrek
2015-05-05 22:33 ` David du Colombier
2015-05-05 22:53 ` Aram Hăvărneanu
2015-05-06 20:55 ` David du Colombier
2015-05-06 21:17 ` Charles Forsyth
2015-05-06 21:26 ` David du Colombier
2015-05-06 21:28 ` David du Colombier
2015-05-06 22:28 ` Charles Forsyth
2015-05-07 3:35 ` erik quanstrom
2015-05-07 6:15 ` David du Colombier
2015-05-07 13:17 ` erik quanstrom
2015-05-08 16:13 ` David du Colombier
2015-05-08 16:39 ` Charles Forsyth
2015-05-08 17:16 ` David du Colombier
2015-05-08 19:24 ` David du Colombier
2015-05-08 20:03 ` Steve Simon
2015-05-08 21:19 ` Bakul Shah
2015-05-09 14:43 ` erik quanstrom
2015-05-09 17:25 ` Lyndon Nerenberg
2015-05-09 17:30 ` Devon H. O'Dell
2015-05-09 17:35 ` Lyndon Nerenberg
2015-05-09 21:54 ` Devon H. O'Dell
2015-05-09 18:20 ` Bakul Shah
2015-05-09 3:11 ` cinap_lenrek
2015-05-09 5:59 ` lucio
2015-05-09 16:26 ` cinap_lenrek
2015-05-09 16:23 ` erik quanstrom
2015-05-10 4:55 ` erik quanstrom
2015-05-10 5:07 ` erik quanstrom
2015-05-10 17:57 ` David du Colombier
2015-05-10 20:18 ` erik quanstrom
2015-05-10 20:19 ` cinap_lenrek
2015-05-10 20:51 ` erik quanstrom
2015-05-10 21:34 ` cinap_lenrek
2015-05-11 1:23 ` erik quanstrom
2015-05-09 16:59 ` erik quanstrom
2015-05-06 22:35 ` Steven Stallion
2015-05-06 23:47 ` Charles Forsyth
2015-05-07 3:38 ` erik quanstrom
2015-05-07 3:43 ` erik quanstrom
2015-05-05 15:07 ` KADOTA Kyohei
2015-05-05 14:47 ` KADOTA Kyohei
2015-05-05 15:46 ` steve
2015-05-05 15:54 ` David du Colombier
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='CAOFTvP+YO-DeOq7Y=iO__MzBELXczsusExkUXcQLykQ-4EcBjg@mail.gmail.com' \
--to=szhilkin@gmail.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).