Minimum latency test

This test measures the minimum latency for a client request - the server establishes a session (connection to DB, etc) and returns a fixed greeting. It should be routinely possible to get latencies below 20ms. Low latency allows smaller more frequent requests from user interface clients, which makes for a more interactive user experience.

This page is also a simple demonstration of dynamically updating web pages by calling the OME server from JavaScript. This is not quite Ajax (Asynchronous JavaScript and XML), but it is how an Ajax application would talk to its server.

This test makes 25 sequential GET requests from the specified OME server URL, and reports the number of milliseconds to receive each response. Requests are issued using XMLHttpRequest as implemented by the sarissa library. A request is first sent to OME::Web::Login, exchanging the supplied username/password for a SessionKey, and setting the SessionKey cookie in the browser. This initial login request is not timed. The 25 requests are then sent to OME::Web::Ping, which sets up (or re-establishes) a session on the server using the client's SessionKey, and responds with a text/plain greeting ("Hi!").

N.B.: The domain (server name) of the OME URL below should match the domain of this page (in the URL above). Some browsers allow scripts in web-pages to contact servers on different domains, while others consider this a security risk.


URL
Username     Password


SessionKey
ms/Req.