LDP/LDP/howto/docbook/openMosix-HOWTO/openMosix_Features.sgml

77 lines
2.1 KiB
Plaintext

<SECT1>
<TITLE>Pros of openMosix</TITLE>
<PARA>
<table><title>Pros of openMosix</title>
<tgroup cols='1' align='left' colsep='1' rowsep='1'>
<tbody>
<row><entry>No extra packages are required.</entry></row>
<row><entry>No code changes to your application are
required.</entry></row>
<row><entry>Simple to install/configure.</entry></row>
<row><entry>On a Red-Hat based system/distro, installing openMosix
is as simple as typing: # rpm -Uvh openMosix*.rpm</entry></row>
<row><entry>DSM is being released soon (late march
2003).</entry></row>
<row><entry>Port to IA-64 as well as AMD-64 is
underway.</entry></row>
<row><entry>It is a clustering platform with more than 10 products
based on it: openMosixView, openMosixWebView, openMosixApplet,
RxLinux, PlumpOS, K12LTSP, LTSP and many others.</entry></row>
<row><entry>openMosix is a product developed by the users themselves
so it's more close to the user by definition.</entry></row>
<row><entry>Node autodiscovery/fail-over daemon already implemented
in the user land tools via multicast messaging.</entry></row>
<row><entry>Aliases for hosts with multiple
interfaces.</entry></row>
<row><entry>Basic routing available (in the rare case where true
multicast routing is undesirable).</entry></row>
<row><entry>Cluster Mask allows to specify to which nodes
a given process can migrate.</entry></row>
</tbody>
</tgroup>
</table>
</PARA>
</SECT1>
<SECT1>
<TITLE>Cons of openMosix</TITLE>
<PARA>
<table><title>Cons of openMosix</title>
<tgroup cols='1' align='left' colsep='1' rowsep='1'>
<tbody>
<row><entry>Kernel dependent.</entry></row>
<row><entry>Shared memory issues (an alpha release of DSM should be
available as of late march 2003).</entry></row>
<row><entry>There are issues with Multiple Threads not gaining
performance.</entry></row>
<row><entry>You won't gain performance when running one single process
such as your web browser on an openMosix Cluster: the process won't
spread itself over the cluster. Except of course your process will
migrate to a more performant machine.</entry></row>
</tbody>
</tgroup>
</table>
</PARA>
</SECT1>
</CHAPTER>