dbstress and dbstresm GPL Applications

dbstress and dbstresm are database stress test applications. They are used to verify the Bbuuzzb database engine/server. dbstress is a single user application with the Bbuuzzb database engine linked right into the executable/binary and dbstresm is a client/server application that expects to connect to dbsrv which is the Bbuuzzb database server.

When either of these programs are executed, they will enter an infinite loop of picking a operation code and attempting to carry it out. These applications use the same operation codes as the db and dbm applications which are defined in the header file dbcomm.h.

Before you can run the dbstress application, you must set up a database engine configuration file called dbeng.cfg with a minimum of the tmp_path, log and catalog entries.

The dbstresm application communicates with the Bbuuzzb database server through TCP sockets (Unix and Windows) or QNX native message passing (QNX 4.x OS). The Bbuuzzb server and the dbstresm application use the socloc interface to manage TCP/IP configuration information (TCP IPC method only).

In order to get dbstresm to successfully connect to the Bbuuzzb database server, the server must already be running and there must also be at least one socloc server (TCP only) and at least one system log server running within the environment. A socloc startup file must also be composed (TCP only). The database configuration file is not required for the dbstresm application.

All configuration files must be located in the same directory as the binary/executable program. The dbstress and dbstresm applications must be executed within their current directory so the program can locate the configuration files.

Both of these programs will output detail on each command operation. The output will, go to the screen and to a log file which is defined in the program code. These stress programs also require two Bbuuzzb test tables. The primary table will be opened when the program is executed and a secondary table will be opened and closed upon demand. Both the dbstress and dbstresm applications require the database catalog feature of the database to be active and uses the logical table names to open the tables. The primary table is called test.primary and the secondary table is called test.alternate.

The dbstress application can be compiled for all stated platforms. The dbstresm application can be compiled on all stated platforms except DOS where there is no TCP IPC method.

Under the Linux/Unix/QNX operating systems, the dbstress application can be compiled using the mkdbstress script. The dbstresm application can be compiled using the mkdbstresm script.

Command Line Syntax

Both the dbstress and dbstresm applications have the same command line syntax, which is:

dbstress|dbstresm [-p primt] [-a altt] [-l logf]

Where primt is the primary table/file name, altt is the alternate table/file name and logf is the output log file name. Note that all parameters are optional. Any parameter that is missing will have its value loaded from the compile default. Also note that the switch character (a dash/hyphen [-] is shown here) depends on the platform the application is running on.

Goto Top | Future Lab Home | Contact Webmaster | Feedback

Copyright © 1999-2006 Future Lab, Last Updated Jun 25, 2006