9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john francis lee <jfl@robinlea.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server speed
Date: Thu, 17 Jul 2014 08:09:39 +0700	[thread overview]
Message-ID: <53C72253.5080606@robinlea.com> (raw)
In-Reply-To: <CAGGHmKHV+Ahnx7WkQvSQ0b_arEQ0bZoCWXM96D-f6e1scvqBHQ@mail.gmail.com>

Not Found

The resource could not be found.

WSGI Server

On 07/17/2014 07:29 AM, Steven Stallion wrote:
> On Wed, Jul 16, 2014 at 6:15 PM,  <kokamoto@hera.eonet.ne.jp> wrote:
>>> That was in an office environment. At home I use
>>> fossil+(plan9port)venti running on linux-based NAS.
>>
>> Do you use wireless LAN?
>> If so you also need wireless bridge?
>> The combination of NAS and venti sounds like charm,
>> because the snmallest config is two machines.
>>
>> How about the power-eating of that machine?
>> Recent low-power machine can do that task?
>
> I've used ReadyNAS appliances at home for almost 10 years. The current
> product line is made up of low-power Atoms. I'm running a RAID5 across
> 4 500G enterprise SATA drives (that should indicate how old this unit
> is pretty well...) I have a wired network primarily in the rack in the
> office at home - I absolutely would not use wireless to connect fossil
> to venti (fossil does *not* cope well with the connection to venti
> dropping).
>
> I switched over to fossil on the ReadyNAS a little over a year ago and
> have had really good luck; not a single crash. Performance has also
> been very good.
>
> It just so happens I wrote a README at the time since it was
> non-obvious how to set it up correctly:
> https://dl.dropboxusercontent.com/u/102312978/FOSSIL
>
> Cheers,
>
> Steve
>


--
John Francis Lee
Thanon Sanam Gila, Ban Fa Sai
79/151 Moo 22 T. Ropwieng
Mueang Chiangrai 57000
Thailand





  parent reply	other threads:[~2014-07-17  1:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  6:13 kokamoto
2014-07-15 13:02 ` Anthony Sorace
2014-07-15 16:30 ` cinap_lenrek
2014-07-15 16:56   ` erik quanstrom
2014-07-16  0:04   ` kokamoto
2014-07-16  0:36     ` kokamoto
2014-07-16 17:26       ` erik quanstrom
2014-07-16 14:23     ` Steven Stallion
2014-07-16 14:53       ` Ramakrishnan Muthukrishnan
2014-07-17  1:13         ` Steven Stallion
2014-07-17 17:13           ` Ramakrishnan Muthukrishnan
2014-07-17 21:44         ` cam
2014-07-16 17:41       ` erik quanstrom
2014-07-16 23:15       ` kokamoto
2014-07-17  0:29         ` Steven Stallion
2014-07-17  0:31           ` Steven Stallion
2014-07-17  1:10             ` john francis lee
2014-07-17  1:09           ` john francis lee [this message]
2014-07-17  1:10           ` Bakul Shah
2014-07-17 16:56           ` erik quanstrom
2014-07-17 18:14             ` Bakul Shah
2014-07-17 18:39               ` erik quanstrom
2014-07-17 19:01               ` Bakul Shah
2014-07-17 19:10                 ` erik quanstrom
2014-07-17 19:26                   ` Bakul Shah
2014-07-16 17:23     ` erik quanstrom
2014-07-16 23:01       ` kokamoto
2014-07-17 17:03         ` erik quanstrom
2014-07-18 16:50           ` hiro
2014-07-18 19:36             ` erik quanstrom
2014-07-18 20:11               ` Bakul Shah

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=53C72253.5080606@robinlea.com \
    --to=jfl@robinlea.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).