<P>Netplex allows you to choose how often the server is allowed to become active, how many simultaneous connections are allowed and the amount of file buffer that's allocated. By adjusting these three parameters, you can control how much of your machine's network bandwidth can be used when clients access the server.</P>
<P>For example, if you have a connection which delivers 64Kb/sec then you could set the <I>Wait</I> field to 50 centiseconds, allow four simultaneous connections and have a 4Kb buffer. This allows a maximum of 32Kb/sec to be used by the server, which is reasonable if you wish to be simultaneously using your machine for network activities.</P>
<P>That said, you must note that the throughput that Netplex can achieve is entirely dependent on your machine and net connection, and different settings will have varying effects depending on what machine you have. For example, using a <I>Wait</I> setting of 0 on my ARM 610 machine, is actually <I>slower</I> than a setting of 1. This happens because Netplex tries to serve data too quickly and ends up just impeding its own perfomance.</P>
<P>It is difficult to give hard and fast rules about what settings will give you in terms of transfer rates - in fact, the best way of checking your settings is to use two locally networked machines and try transferring a large file between the two.</P>
<P>General points:</P>
<UL>
<LI>Don't set the Wait to zero - it often throttles the server.
<LI>Don't use a file buffer of more than 12Kb - the Internet module uses 12Kb buffers by default and using more than that will degrade perfomance.
<LI>Use a smaller buffer and a quicker <I>Wait</I> time in preference to a large buffer and slower Wait time.
