📄 00000135.htm
字号:
through April 12, 1999, there were no
<BR>messages posted to the Usenet asking about memory or buffer tuning for large <BR>memory machines.
<BR>
<BR>3) Use of inappropriate kernel version The Linux 2.2.2 kernel's network stack <BR>had severe performance problems
<BR>interacting with Microsoft clients. For more information, see the Kernel <BR>Traffic newsletter for March 4, 1999. Given
<BR>the known problems with the 2.2.2 kernel, either the 2.2.1 kernel should have <BR>been used, or the 2.2.3 kernel should have
<BR>been used.
<BR>
<BR>4) Allocation of Swap not Specified Linux requires a swap partition for best <BR>operation. If the swap space is allocated on
<BR>multiple drives (one swap partition per drive), the Linux VM system will <BR>utilize the drives in parallel, effectively using
<BR>them as a RAID0 (striping) array. Unfortunately, we don't know how swap space <BR>was allocated in the Mindcraft test, and
<BR>thus cannot duplicate their configuration.
<BR>
<BR>C. Samba Configuration Problems
<BR>
<BR>1) Recompilation of Samba with inappropriate settings: Red Hat Software has <BR>the Samba 2.0.x server available
<BR>precompiled on their web site as a pre-packaged upgrade to go along with the <BR>2.2 kernel. For some reason Mindcraft
<BR>chose to use their own custom compiled package which was not compiled with <BR>the optimizations that Red Hat compiles
<BR>into their own packages. In particular, the Mindcraft package was recompiled <BR>with the -O option rather than the -O2
<BR>option that Red Hat uses. In other words, the compiled binary was compiled <BR>with options that would generally make it
<BR>noticably slower than the one shipped by Red Hat Software. To quote the GNU <BR>"gcc" documentation regarding the
<BR>"-O2" option:
<BR> As compared to `-O', this option increases both compilation time and the <BR>performance of the generated code.
<BR>
<BR>For a fair test, either the Red Hat provided Samba should have been used, or <BR>if a 'performance tweak' was needed to
<BR>insure that both systems were optimized, the "egcs" C compiler (a standard <BR>part of Red Hat Linux) should have been
<BR>used with the -mpentiumpro option to optimize the resulting code to take <BR>advantage of Pentium II features.
<BR>
<BR>2) Inappropropriate use of the widelinks=no option: Andrew Tridgell of the <BR>Samba team reports that setting
<BR>"widelinks=no" option will noticably slow performance of the Samba server. <BR>The "widelinks=no" option is a security
<BR>feature intended for mixed-use systems, rather than for dedicated server use. <BR>For dedicated server use it is unnecessary,
<BR>since Windows clients are unable to set filesystem links on a Samba server <BR>(only interactive Linux users can do so).
<BR>
<BR>Please note that Jeremy Allison of the Samba team reports no queries on the <BR>Samba mailing lists or at the Samba home
<BR>page that could have been about tuning Samba for use on large file servers <BR>during the time period in question.
<BR>
<BR>D. Apache Configuration Problems
<BR>
<BR>1) Inappropriate compilation:Again, for some unknown reason Mindcraft chose <BR>to re-compile Apache rather than
<BR>use the default Red Hat version. This makes it difficult to compare "out of <BR>box" performance. If the purpose was to
<BR>improve performance, using "egcs" to recompile it with the -mpentiumpro <BR>optimizations would have accomplished
<BR>much more. Some Apache experts claim as much as 30% improvement by compiling <BR>Apache with the Pentium Pro
<BR>optimizations.
<BR>
<BR>2) Inappropriate settings for StartServers and SpareServers: If you are <BR>running an enterprise server expecting 150
<BR>or more simultaneous connections, you would set StartServers to 150 or <BR>greater. It's not as if there is a shortage of
<BR>memory, after all.
<BR>
<BR>3) Inadequate information to duplicate the test:Access to copies of the httpd <BR>configuration files is needed to further
<BR>duplicate the test and diagnose the problems found there. For example, the <BR>"collapse" of the Apache server described
<BR>therein is counter to what every other performance survey of Apache has <BR>found, which is that Apache reaches a
<BR>maximum and then mildly degrades as overload continues.
<BR>
<BR>A search of the DejaNews archives shows that a "<A HREF="mailto:will@whistlingfish.net"">will@whistlingfish.net"</A> <BR>posted a query about this "collapse" problem.
<BR>Unfortunately, it does not give enough information to make any sort of <BR>diagnosis possible (probably why it recieved no
<BR>meaningful responses).
<BR>
<BR>III. Non-Technical Problems with Study
<BR>
<BR>The overall tone of the report was rather unfortunate. For example:
<BR>
<BR>We posted notices on various Linux or Apache newsgroups and received no <BR>relevant responses
<BR>
<BR>This implies that they made multiple requests for help ("notices") and that <BR>the Linux community, in violation of its
<BR>reputation for excellence in technical support, dropped the ball. In <BR>actuality, exhaustive searching of the DejaNews
<BR>archives by a team of Linux users has identified one single message as a <BR>possible candidate for these "notices". It was
<BR>cross-posted under a different title between a Linux newsgroup and the Apache <BR>newsgroup, and recieved a reply which
<BR>basically requested more information (albeit in a rather impatient manner). <BR>If the requested information was ever
<BR>supplied, it was not ever posted to the newsgroup where other members of the <BR>Linux community could add their own
<BR>comments.
<BR>
<BR>The report is full of similar statements which could be interpreted as <BR>showing partiality or being inappropriate. Given
<BR>the fact that this study was funded by Microsoft Corporation, Mindcraft <BR>should have taken special care to protect their
<BR>reputation by appearing as impartial as possible.
<BR>
<BR>IV. Conclusions
<BR>
<BR>We welcome the opportunity to work with Mindcraft to resolve these glaring <BR>issues and produce a quality analysis. The
<BR>Linux community is extremely interested in a fair, impartial analysis of the <BR>performance of Linux as compared with
<BR>competitors. Such analysis has been very valuable in the past, and promises <BR>to be equally valuable to the technical
<BR>advancement of Linux in the future.
<BR>
<BR>Unfortunately, given the severe technical shortcomings of this report, we <BR>must respectfully request that Mindcraft
<BR>withdraw it until such issues are resolved. A report which is perceived to be <BR>biased is not in the best interests of either
<BR>Mindcraft or its client, and may in fact be embarrasing to both.
<BR>
<BR>Eric Lee Green
<BR>Last modified: Fri Apr 16 12:52:04 EDT 1999 <BR> <BR>-- <BR>※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.118.66.88] <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -