<!-- MHonArc v2.4.4 --> <!--X-Subject: RE: [MUD-Dev] Sockets --> <!--X-From-R13: Qlaor eh Fnera <plaorNzhd.bet> --> <!--X-Date: Fri, 14 May 1999 01:20:10 -0700 --> <!--X-Message-Id: 199905130824.DAA12953#laurel,actlab.utexas.edu --> <!--X-Content-Type: text/plain --> <!--X-Head-End--> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html> <head> <title>MUD-Dev message, RE: [MUD-Dev] Sockets</title> <!-- meta name="robots" content="noindex,nofollow" --> <link rev="made" href="mailto:cynbe#muq,org"> </head> <body background="/backgrounds/paperback.gif" bgcolor="#ffffff" text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000"> <font size="+4" color="#804040"> <strong><em>MUD-Dev<br>mailing list archive</em></strong> </font> <br> [ <a href="../">Other Periods</a> | <a href="../../">Other mailing lists</a> | <a href="/search.php3">Search</a> ] <br clear=all><hr> <!--X-Body-Begin--> <!--X-User-Header--> <!--X-User-Header-End--> <!--X-TopPNI--> Date: [ <a href="msg00244.html">Previous</a> | <a href="msg00246.html">Next</a> ] Thread: [ <a href="msg00242.html">Previous</a> | <a href="msg00253.html">Next</a> ] Index: [ <A HREF="author.html#00245">Author</A> | <A HREF="#00245">Date</A> | <A HREF="thread.html#00245">Thread</A> ] <!--X-TopPNI-End--> <!--X-MsgBody--> <!--X-Subject-Header-Begin--> <H1>RE: [MUD-Dev] Sockets</H1> <HR> <!--X-Subject-Header-End--> <!--X-Head-of-Message--> <UL> <LI><em>To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A></LI> <LI><em>Subject</em>: RE: [MUD-Dev] Sockets</LI> <LI><em>From</em>: Cynbe ru Taren <<A HREF="mailto:cynbe#muq,org">cynbe#muq,org</A>></LI> <LI><em>Date</em>: Thu, 13 May 1999 03:24:58 -0500</LI> <LI><em>Reply-To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A></LI> <LI><em>Sender</em>: <A HREF="mailto:mud-dev-admin#kanga,nu">mud-dev-admin#kanga,nu</A></LI> </UL> <!--X-Head-of-Message-End--> <!--X-Head-Body-Sep-Begin--> <HR> <!--X-Head-Body-Sep-End--> <!--X-Body-of-Message--> <PRE> Caliban Tiresias Darklock <caliban#darklock,com> joked: | If multi-processing O/Ss were not efficient, then we would not run them. | | Therefore, we run an O/S because it is efficient. | | Therefore, if an O/S is being run, it must be efficient. | | The world's most-run operating system is Microsoft Windows. | | Therefore, Microsoft Windows is the world's most efficient operating system. | | Go Bill! Most efficient at extracting money from the rest of the world, clearly! I think perhaps a bit more thought and attention need to be devoted to -what- an OS or software paradigm is efficient at. We're swimming in hardware capacity these days -- the costs of PCs are collapsing in large part because we finally do have more CPU oomph than we know how to effectively apply, by and large. IMHO, the low-level CPU efficiency differences between using multiple threads blocking on sockets vs a single thread and select() are entirely negligible at this point: Nobody is -ever- going to select your design because you got that decision "right". What matters a hell of a lot more is which choice will lead to the most robust, understandable, maintainable, effective application. We all learned to program when CPU bandwidth was much more expensive than it is now: We're habituated to credit it with far more importance than it now deserves. The efficiency issues we should be worrying about now are efficient use of programmer time, efficient use of end-user time, efficient distribution of bugfixes and the like -- not efficient use of CPUs which are anyhow 98% idle. I've personally got about (I've lost count) 16 CPUs on the internet at the moment, any one of them probably capable of carrying all of kernel.org's traffic, and I'd bet none of them less than 98% idle as I type this. (Using no less then three of those CPUs spread over two states to handle each character typed, but who cares?) Efficient use of today's CPUs means applying that 98% idle time to do something useful for the user, not upping it to 99% idle time. E.g., check out "A Review of Experiences with Reliable Multicast" at <A HREF="http://cs-tr.cs.cornell.edu/">http://cs-tr.cs.cornell.edu/</A> and decide what the implications are for mud-dev: Is reliable multicast appropriate? Practical? Desirable? Does it make it too easy for a single malicious participant to bring everything to a halt? How much consistency between the views presented to different participants is required? Desirable? Practical? Possible? Just my two bits. :) Cynbe _______________________________________________ MUD-Dev maillist - MUD-Dev#kanga,nu <A HREF="http://www.kanga.nu/lists/listinfo/mud-dev">http://www.kanga.nu/lists/listinfo/mud-dev</A> </PRE> <!--X-Body-of-Message-End--> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <ul compact><li><strong>Follow-Ups</strong>: <ul> <li><strong><A NAME="00269" HREF="msg00269.html">[MUD-Dev] Re[2]: [MUD-Dev] Sockets</A></strong> <ul compact><li><em>From:</em> Travis Casey <efindel#io,com></li></ul> <li><strong><A NAME="00257" HREF="msg00257.html">Re: [MUD-Dev] Sockets</A></strong> <ul compact><li><em>From:</em> Mark Gritter <mark#erdos,Stanford.EDU></li></ul> <li><strong><A NAME="00253" HREF="msg00253.html">RE: [MUD-Dev] Sockets</A></strong> <ul compact><li><em>From:</em> Caliban Tiresias Darklock <caliban#darklock,com></li></ul> </UL></LI></UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00244.html">Re: [MUD-Dev] Sockets</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00246.html">Re: [MUD-Dev] Dynamically changing room descriptions</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00242.html">RE: [MUD-Dev] Sockets</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00253.html">RE: [MUD-Dev] Sockets</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="index.html#00245"><STRONG>Date</STRONG></A></LI> <LI><A HREF="thread.html#00245"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> <ul><li>Thread context: <BLOCKQUOTE><UL> <LI><STRONG>RE: [MUD-Dev] Sockets</STRONG>, <EM>(continued)</EM> <ul compact> <ul compact> <ul compact> <LI><strong><A NAME="00224" HREF="msg00224.html">RE: [MUD-Dev] Sockets</A></strong>, Daniel Garcia <a href="mailto:dgarcia#hollyfeld,org">dgarcia#hollyfeld,org</a>, Wed 12 May 1999, 22:36 GMT </LI> </ul> </ul> <LI><strong><A NAME="00220" HREF="msg00220.html">RE: [MUD-Dev] Sockets</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Wed 12 May 1999, 22:27 GMT </LI> <LI><strong><A NAME="00231" HREF="msg00231.html">RE: [MUD-Dev] Sockets</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Fri 14 May 1999, 07:34 GMT </LI> <LI><strong><A NAME="00242" HREF="msg00242.html">RE: [MUD-Dev] Sockets</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Fri 14 May 1999, 08:15 GMT </LI> <LI><strong><A NAME="00245" HREF="msg00245.html">RE: [MUD-Dev] Sockets</A></strong>, Cynbe ru Taren <a href="mailto:cynbe#muq,org">cynbe#muq,org</a>, Fri 14 May 1999, 08:20 GMT <UL> <LI><strong><A NAME="00253" HREF="msg00253.html">RE: [MUD-Dev] Sockets</A></strong>, Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Sat 15 May 1999, 09:31 GMT <UL> <LI><strong><A NAME="00272" HREF="msg00272.html">Re: [MUD-Dev] Sockets</A></strong>, Travis Casey <a href="mailto:efindel#io,com">efindel#io,com</a>, Sun 16 May 1999, 21:10 GMT </LI> <LI><strong><A NAME="00293" HREF="msg00293.html">RE: [MUD-Dev] Sockets</A></strong>, Adam Wiggins <a href="mailto:adam#angel,com">adam#angel,com</a>, Tue 18 May 1999, 06:37 GMT </LI> </UL> </LI> <LI><strong><A NAME="00257" HREF="msg00257.html">Re: [MUD-Dev] Sockets</A></strong>, Mark Gritter <a href="mailto:mark#erdos,Stanford.EDU">mark#erdos,Stanford.EDU</a>, Sat 15 May 1999, 09:31 GMT </LI> </UL> </LI> </ul> </LI> </UL></BLOCKQUOTE> </ul> <hr> <center> [ <a href="../">Other Periods</a> | <a href="../../">Other mailing lists</a> | <a href="/search.php3">Search</a> ] </center> <hr> </body> </html>