TX Text Control ActiveX Server Performance

TX Text Control ActiveX Server has been specifically designed to run in server side applications and therefore does not have a user interface. All interactions with TX Text Control ActiveX Server are performed programmatically from application code. TX Text Control ActiveX Server is completely invisible to the end-user, making it idea for batch processing or printing large volumes of documents.

Benchmarking TX Text Control ActiveX Server

Three critical aspects of server-side document processing are:

1. Speed
2. Reliability
3. Stability

We therefore set up a number of tests in the TX Text Control Laboratory to examine these three major characteristics.

An average request took less than 150 milliseconds.

The benchmark tests simulated concurrent requests to TX Text Control ActiveX Server. An ASP script loaded a three page document, searched through the entire document for a textual string, using the Find method, and replaced it with another string. Then, the document was exported as RTF and saved on the server in another directory. The benchmark time includes the file loading process, the find and replace and the file saving.

This first graph illustrates the complete duration of one test. The test was repeated four times – each one with a different number of requests: 20, 50, 100 and 150 requests. To measure the response times, we used the benchmarking tool ApacheBench from the Apache Software Foundation (www.apache.org). As we were intentionally performing the test on a low range server* to prove that very acceptable results can be achieved with minimum hardware, we set the concurrent request rate to only 10.

The second graph illustrates the number of requests per second that are executed by TX Text Control ActiveX Server. It shows that in the beginning, there are about 4.6 requests per second. The number of requests was increased and saturation finally arrived at an average of 7.6 requests per second.

This final graph illustrates that the time per request levels off at an average value of 130 milliseconds. This is the time a request takes on average.

Wrap up

The values presented on this page are of course dependant upon the server hardware and the connection speed between the clients and the server. We used a low powered server and a 10Mbit LAN to show how TX Text Control ActiveX Server works under minimum hardware conditions. Naturally, the faster the hardware, the faster TX Text Control ActiveX Server will perform.* Server Windows XP Professional IIS 5.1, Intel Celeron 1.7 GHz, 256 MB RAM