TATP (Telecommunication Application Transaction Processing Benchmark) generates a transactional load over parallel client connections, targeted at a database system under test. It is modeled after a mobile network application HLR (Home Location Register).

The Telecommunication Application Transaction Processing (TATP) benchmark is designed to measure the performance of an relational DBMS/OS/Hardware combination in a typical telco application.
The benchmark generates a flooding load on a database server. This means that the load is generated up to the maximum throughput point that the server can sustain. The load is generated by issuing pre-defined transactions run against a specified target database. The target database schema is made to resemble a typical Home Location Register (HLR) database in a mobile phone network. The HLR is a database that mobile network operators use to store information about the subscribers and the services thereof.

A typical test run consists of three phases: (1) database population, (2) test ramp-up, and (3) performance measurement (sampling). The database is populated with initial data before the actual benchmark is started. The data is generated in a way that satisfies the given statistical distributions in key values, and cardinalities, as specified in [1].

The timing of a test run involves the ramp-up and sampling (measurement) phases. For example, following the ramp-up time of 10 min, the sampling phase is run for 20 minutes. For big disk-based databases, both periods should be long enough to expose stable behavior. In in-memory databases, the test periods can be shorter (say, 5 + 10 minutes) due to the fact that there is no page buffer pool to warm up, and the system attains a quiesced state in a shorter time.

Requirements:
* ODBC

The license of this software is Free, you can free download and free use this database management software.