From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from feline.systems ([99.23.220.214]) by ur; Sat Jun 4 02:31:46 EDT 2016 Date: Sat, 4 Jun 2016 02:31:41 -0400 From: BurnZeZ@feline.systems To: 9front@9front.org Subject: Re: [9front] State of the 9front mailing list archives Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: browser CSS table-based browser On Fri Jun 3 14:46:01 EDT 2016, sl@stanleylieber.com wrote: > In my previous mail I was responding more to the same discussion that gets held over and over on IRC by the same people about how accessing the mailing list archive is awkward and slow. That's expected with latency and any protocol that requires a lot of back and forth. meiling% 9fs 9front >[2]/dev/null meiling% time ls -l /n/9front/lists/9fans >/tmp/foo 0.90u 0.08s 120.38r ls -l /n/9front/lists/9fans meiling% wc -l /tmp/foo 93845 /tmp/foo meiling% echo 93845 / 120.38 | hoc 779.573018774 # files per second meiling% ip/ping -n 5 9front.org sending 5 64 byte messages 1000 ms apart to icmp!9front.org!1 0: rtt 49053 µs, avg rtt 49053 µs, ttl = 245 1: rtt 47224 µs, avg rtt 48138 µs, ttl = 245 2: rtt 47660 µs, avg rtt 47979 µs, ttl = 245 3: rtt 47340 µs, avg rtt 47819 µs, ttl = 245 4: rtt 47084 µs, avg rtt 47672 µs, ttl = 245 meiling% echo 120.38 / 0.04672 | hoc 2576.62671233 # number of possible round trips meiling% echo 93845 / 2576 | hoc 36.4305124224 # estimated files per round trip # /tmp/cache is an arbitrary directory I store some crap meiling% time ls -l /tmp/cache >/tmp/bar 0.07u 0.01s 0.09r ls -l /tmp/cache meiling% wc -l /tmp/bar 6161 /tmp/bar meiling% echo 6161 / 0.09 | hoc 68455.5555556 # files per second, locally This assumes we send and receive messages, one at a time. It's better than I thought, but I suppose it doesn't scale well to directories with hundreds of thousands of files, or a higher latency link. What about increasing the speed of light?