From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] anyone put their venti on an SSD?
Date: Sat, 4 May 2013 11:09:25 -0700 [thread overview]
Message-ID: <CAGGHmKGZOjt7G3OaM06G4HLBjyHhaPiBU0VZ=RHjFWmak2KVvg@mail.gmail.com> (raw)
In-Reply-To: <aeb00f36cd224ebfcc14f4ebf308a051@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Makes sense. Moving to plan9port had more to do with making better use of
the ReadyNAS in the rack than anything else. The performance was a nice if
unexpected side-effect.
On Friday, May 3, 2013, erik quanstrom wrote:
> On Fri May 3 23:27:40 EDT 2013, sstallion@gmail.com <javascript:;> wrote:
>
> > I had originally used a Crucial 32GB SSD years ago and swapped to a 55GB
> > OCZ enterprise drive (using sdahci). More recently I've moved my venti
> > arenas over to plan9port and have switched over to using the entire SSD
> for
> > fossil. So far this has been faster than running venti natively - though
> I
> > still take a replica each night out of paranoia.
>
> there are many components to the performance here, but i can think of at
> least one simple issue. plan 9 loopback tcp can be pretty slow due to
> scheduling
> issues. (induced by the structure of tcp, not any issue with the
> scheduler.)
> my atom (which is slightly worse than a d525) gets
>
> ladd; nettest -l -n 10000
> tcp!192.168.0.136!39769 count 10000; 81920000 bytes in 2.649575 s
> @ 29.5 MB/s (0ms)
>
> so i would imagine that working out how to post a fd to srv would really
> help
> a lot. not to mention, taking some funk out of configuring the network on
> boot. :-)
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
prev parent reply other threads:[~2013-05-04 18:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 14:19 Steve Simon
2013-05-03 14:28 ` a
2013-05-03 20:59 ` geoff
2013-05-03 21:51 ` Matthew Veety
2013-05-03 21:58 ` cinap_lenrek
2013-05-04 1:59 ` erik quanstrom
2013-05-04 4:17 ` cinap_lenrek
2013-05-04 6:17 ` erik quanstrom
2013-05-03 23:59 ` Charles Forsyth
2013-05-04 1:31 ` cinap_lenrek
2013-05-04 1:41 ` Devon H. O'Dell
2013-05-04 1:47 ` Lyndon Nerenberg
2013-05-04 1:51 ` erik quanstrom
2013-05-04 1:57 ` Lyndon Nerenberg
2013-05-04 2:00 ` erik quanstrom
2013-05-04 2:03 ` Lyndon Nerenberg
2013-05-04 2:13 ` Kurt H Maier
2013-05-04 2:17 ` erik quanstrom
2013-05-04 5:50 ` Charles Forsyth
2013-05-04 6:22 ` Bakul Shah
2013-05-04 1:16 ` Lyndon Nerenberg
2013-05-04 1:43 ` erik quanstrom
2013-05-04 1:50 ` Lyndon Nerenberg
2013-05-04 3:41 ` Steven Stallion
2013-05-04 4:19 ` cinap_lenrek
2013-05-04 4:46 ` Lyndon Nerenberg
2013-05-04 3:26 ` Steven Stallion
2013-05-04 6:44 ` erik quanstrom
2013-05-04 18:09 ` Steven Stallion [this message]
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='CAGGHmKGZOjt7G3OaM06G4HLBjyHhaPiBU0VZ=RHjFWmak2KVvg@mail.gmail.com' \
--to=sstallion@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).