Read Me for XBPerf

(c) Wolfgang Riedmann 1994-2001 
http://www.riedmann.it

XBPerf tries to do some xBase performance tests to measure the xBase performance
of a system or a network.

It does this with the following tests:

- append 50000 records to an empty database
- create three orders to this database
- do 50000 random seeks on this database
- update all records, changing the order value
- do a sequential read without an active order
- do a sequential read with an active order

The source for the program is common for the CA-VO version and both Clipper 
versions.

The CA-VO version (XBPerf32.EXE) is compiled with CA-VO 2.5b-3, DBFCDX
The Clipper real mode version (XBperf.exe) is compiled with Clipper 5.3b and Blinker
The Clipper protected mode version (XBperfP.exe) is linked with ExoSpace

I have done this program because a some of my clients have noted that after 
a network upgrade from 10 Mbps to 100 Mbps, the Clipper apps run slow as before, 
or in one case a lot lower, but the Windows apps were significantly faster.

You can use distribute and modify this app freely, but you cannot charge for it, and 
you cannot remove the copyright from it.

The app creates the DBF and CDX files in the current directory, and updates a 
XBPerf.LOG with the results.

If you wish to make your tests with a different number of records, you can modify
one single parameter to accomplish this.

There is no strong typed parameter in this program as the source is the same for all
versions.

Enjoy!

Wolfgang
wolfgang@riedmann.it

---------------------------------------------------------------------------------
Addendum for 8. August 2010

I have reworked the XBPerf32.exe as DOS applications seem dead now (they don't run on Win64).
The Windows application was rewritten to be a normal console app, with its own icon and
title bar. The change to a Console app was necessary because I have ported the program to
CA-VO 2.8 SP2, and there the QOut() function is not available anymore.
The number of records is now configurable in the (automatically) created ini file.

The DOS (both real and protected mode) versions of the program remained unchanged.

