| MUD Client Speed Benchmarks
These speed tests were performed running on a Thinkpad 560 (120 Mhz
Pentium) with 20 MB RAM, running Windows 95, connected to the Internet via 10Mbit/s
ethernet. Screen was in 800x600 resolution, with 16 bit color. Faster times can be
obtained by lowering screen resolution and/or number of colors.
MUD test was performed connected to the Highlands II MUD. Telnet
test was performed connected to a telnet server running on a HP-735 workstation.
zMUD Version speeds (UPDATED 8-Apr-99)
The main test is to load a script containing about 36 triggers (the
actual triggers that I MUD with), then use the #SEND command to display a previously
captured log file (4300 lines) to the screen. The Memory columns shown the memory used by
zMUD before and after the test. The ^Q test is the time displayed when Control-Q is
pressed (a timing function that has been built into zMUD for the last few versions). The
#SEND column is the number of seconds used to display the log file. For the ^Q test, the
Scroll Amount is set to 5. For the #SEND test, Scroll Amount is set to zero (since most
old versions forced Scroll Amount to zero when using #SEND). For very old versions where
#SEND wasn't available (2.91, 2.0) or not working (4.30) then #READ was used, which makes
the times a bit slower for those versions. In later versions where the size of the
buffer can be set, a default size of 1,000 lines is used. In versions 5.4x and
greater, all plugins are unloaded before testing.
MUD/Telnet Client Scrolling Speed Test
- Updates screen after each line is received. This results in smooth,
but very slow scrolling and is equivalent to zMUD Scroll Amount setting of 1.
- Does not support ANSI color codes
- Runs in Console mode of Windows. This results in faster scrolling,
but application is not a true GUI Windows client.
- Only updates screen when entire buffer is received from the MUD,
resulting in very jerky scrolling. This is equivalent to zMUD Scroll Amount setting of 0.
Send 20 look commands (abbreviated with l) to the MUD, followed by
an inv command. This was done in a quiet room in the MUD School of Highlands II which has
very little lag. Time is from pressing Enter after the first look command until the MUD
displays the results of the inv command. Several tests are performed and the results are
averaged and rounded to the nearest second. All clients are run with their screen size
maxmized. Note that Console mode clients (Note 3) allow a smaller number of lines on the
screen, resulting in faster scrolling. If the default font is not fixed-space, Courier
font is selected. Otherwise clients are run with the default settings obtained after a
clean installation. Note that on a 28,800 baud modem, approximately 4 seconds is
required just to transfer the data from the MUD.
||59/12 secs (2)
|Local HP console
- zMUD v4.34a hangs when displaying a large amount of text over a fast
network connection, so a time could not be determined.
- CRT takes 59 seconds to display the termcap file when directed
connected to the client. If connected via an intermediate gateway, CRT speeds up to 12
seconds. This speed difference is due to its method of screen updating. Normally, CRT
updates the screen after every line, resulting in slow display. When an intermediate
server is used, text is buffered so that CRT updates after every buffer is received,
resulting in faster scrolling. The syslog test was only done using an intermediate server
to show the best-case timing.
- GMUD does not support telnet option negotiation, so a telnet
connection to this server could not be made
This test was performed over a high-speed ethernet connection,
rather than the 28,800 modem used in the previous tests. Telnet connection was made
to HP-UX server and the 'cat' command was used to display large files.
- termcap test
- cat /etc/termcap (43,049 byte file). Lines do not wrap
- syslog test
- cat /var/adm/syslog/syslog.log (20,746 byte file) Many lines in this
This page was last updated on .