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. <span></span><br><br>On Friday, May 3, 2013, erik quanstrom  wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri May  3 23:27:40 EDT 2013, <a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;sstallion@gmail.com&#39;)">sstallion@gmail.com</a> wrote:<br>

<br>
&gt; I had originally used a Crucial 32GB SSD years ago and swapped to a 55GB<br>
&gt; OCZ enterprise drive (using sdahci). More recently I&#39;ve moved my venti<br>
&gt; arenas over to plan9port and have switched over to using the entire SSD for<br>
&gt; fossil. So far this has been faster than running venti natively - though I<br>
&gt; still take a replica each night out of paranoia.<br>
<br>
there are many components to the performance here, but i can think of at<br>
least one simple issue.  plan 9 loopback tcp can be pretty slow due to scheduling<br>
issues.  (induced by the structure of tcp, not any issue with the scheduler.)<br>
my atom (which is slightly worse than a d525) gets<br>
<br>
        ladd; nettest -l -n 10000<br>
        tcp!192.168.0.136!39769 count 10000; 81920000 bytes in 2.649575 s @ 29.5 MB/s (0ms)<br>
<br>
so i would imagine that working out how to post a fd to srv would really help<br>
a lot.  not to mention, taking some funk out of configuring the network on<br>
boot.  :-)<br>
<br>
- erik<br>
<br>
</blockquote>