MySpeed Server is a Java applet that enables
you to quickly and easily provide
broadband speed testing to your end users.
MySpeed will use your existing web server as
the server side code -- a huge plus in many secured
environments that do not allow server applications
to be installed.
Quick Start: Extract the files from the
downloaded myspeed.zip trial
kit and place them into a folder on your web server.
Then view the readme.html file on your
web server using your web browser (eg: http://yourserver/myspeed/readme.html)
and try the many MySpeed usage examples included
in the kit. The examples demonstrate several MySpeed
example pages with your licensed version.
MySpeed Server Professional: The Professional version of MySpeed includes all features of the
standard version, plus the features below. A key
component of the Professional version is the MySpeedServer.war Java
Servlet server-side application for added functionality
and increased test accuracy.
MySpeed Server NOC Edition: The NOC
Edition includes all features of the
Professional version, plus a Remote Test Agent
component to perform automated synthetic bandwidth tests from
Deploying MySpeed: After reviewing MySpeed
on your web server (see Quick Start above),
you have some decisions to make before deploying
MySpeed onto a production server:
- Web Server: While
MySpeed will work on almost any web server,
web server is preferred and recommended
since it provides the most accurate upload
test results (details).
- data.bin size: We
recommend replacing the kit 1.2 MB data.bin file
with a 10 MB file that you create (instructions).
This improves the HTTP download speed test
results on broadband connections.
- HTTP vs socket tests: By
default, MySpeed will use your web server
as the only server side software to perform
HTTP download and upload speed tests. This
works very well up to around 100 Mbps for
downloads and 10 Mbps for uploads. However,
by installing the MySpeedServer.war Java
Servlet (a MySpeed Professional feature),
you gain 'socket' based download and upload
speed tests, which works well past 100 Mbps
for both downloads and uploads.
- Reporting: By
installing the MySpeedServer.war Java
Servlet (a MySpeed
Server Professional feature),
you gain server-side
reporting. Add end users names, or any
other text identifier you choose, into reports
by using the Session
ID / Name feature.
- INI settings: There
are many optional configuration parameters
within MySpeed which can be set or changed
to fully modify the MySpeed GUI (colors,
text strings, etc). Edit the MySpeed myspeed.bin INI
file (a 16-bit Unicode file) using notepad.exe (Windows)
or vi (Unix) and review the comments
(lines beginning with '#') in the file for
- Required Files: The
files needed on your web server to deploy
MySpeed Server are:
speedkey.bin (version 5.3 and later)
web page(s) incorporating the MySpeed applet
code (see below)
Customize the MySpeed web page: You can
easily incorporate the MySpeed applet in your
own web pages by including the HTML applet code
below in your web page between the <body></body> tags.
The code below may be copied from the example ‘index.html’ page
included in the MySpeed kit.
<table width=600 height=400><tr><td><applet
MAYSCRIPT name="myspeed" code="myspeed.class" archive="myspeed.jar" width=600
<param name="archive" value="myspeed.jar">
<center><a href="http://www.java.com">Java support is required to
automate processes such as analysis of a VoIP
connection or running continuous speed tests.
into your own MySpeed web pages between the <head></head> tags,
or modify the example pages.
Setting paramater values in the MySpeed
web page. Any parameter in the myspeed.bin INI
file can be overridden by setting a MySpeed
HTML applet paramater. Many of the MySpeed
example HTML files use this technique to create
custom behaviors on a page by page basis.
For example the HTML below can be inserted
within the <applet></applet> tags
to set the speed test to Automatic Start mode.
<param name="start" value="*">
Using multiple configurations: It
is possible to create multiple myspeed.bin INI
files with different parameter settings and refer
to the specific INI file in the web page HTML
within the <applet></applet> tags.
For example, the code below would use a user-created internal.bin file
in place of the myspeed.bin INI file
for the web page:
<param name="myspeed.bin" value="internal.bin">