From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Fri, 18 Feb 2011 14:26:32 EST." References: <201102181445.41877.dexen.devries@gmail.com> <201102181753.30125.dexen.devries@gmail.com> <7769a67a9fbc1fae2186ff9315457e0d@ladd.quanstro.net> <20110218191509.552355B77@mail.bitblocks.com> From: Bakul Shah Date: Fri, 18 Feb 2011 11:46:58 -0800 Message-Id: <20110218194658.8BEA75B77@mail.bitblocks.com> Subject: Re: [9fans] Modern development language for Plan 9, WAS: Re: RESOLVED: recoving important header file rudely Topicbox-Message-UUID: b1409954-ead6-11e9-9d60-3106f5b1d025 On Fri, 18 Feb 2011 14:26:32 EST erik quanstrom wrote: > > On a slightly different tangent, 9p is simple but it doesn't > > handle latency very well. To make efficient use of long fat > > pipes you need more complex mechanisms -- there is no getting > > around that fact. rsync & hg in spite of their complexity > > beat the pants off replica. Their cache behavior is not very > > relevant here. Similarly file readahead is usually a win. > > i don't think that it makes sense to say that since replica > is slow and hg/rsync are fast, it follows that 9p is slow. It is the other way around. 9p can't handle latency so on high latency pipes programs using 9p won't be as fast as programs using streaming (instead of rpc). Granted that there are many other factors when it comes to hg & replica but latency is a major one. > similarly, you blame c++ compilers for excessive inlining. I am suggesting modern compilers should ignore the inline keyword and be cache aware. For the same reason as why the register keyword is mostly ignored. People are wont to use inlining in the hope of improving performance (just as they used register). Sometime it is better to fix a program than try educating the hordes. Actually what I'd really like to suggest is C++ shouldn't be used at all :-)