TATP, or the Telecommunication Application Transaction Processing Benchmark is an Open Source workload designed specifically for high-throughput applications.
The benchmark is well suited for in-memory database performance analysis and system comparison.
The TATP benchmark simulates a typical Home Location Register (HLR) database used by a mobile carrier. The HLR is an application mobile network operators use to store all relevant information about valid subscribers, including the mobile phone number, the services to which they have subscribed, access privileges, and the current location of the subscriber's handset.
Every call to and from a mobile phone involves look ups against the HLRs of both parties, making it a perfect example of a demanding, high-throughput environment where the workloads are pertinent to all applications requiring extreme speed: telecommunications, financial services, gaming, event processing and alerting, reservation systems and so on.
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 composed of pre-defined transactions run against a specified target database.
The benchmark uses four tables and a set of seven transactions that may be combined in different mixes. The most typical mix is a combination of 80% or read transactions and 20% of modification transactions.
The implementation of the TATP load generator is DBMS vendor agnostic. It has been successfully used with various makes of database systems.
Requirements:
· ODBC
What's New in This Release: [ read full changelog ]
· A new TATP command line option "-h" to print the usage help
· A new TATP command line option "-a" (for "add") whereby the missing TIRDB mandatory
· column values (hardware.hardware_id, operating_systems.name & version, _databases.name & version) are extracted from the DDF file.
· Adaptive connect info for the target database and TIRDB. The connect info can given either in the data source name format (DSN=) or as a direct connect string. The latter one is to be used especially with directly linked drivers.
· Added the incremental population mode: populate incrementally min_subscriber_id=500001
· New test sequence directive in TDF: execute file="foo.sql"
· The given SQL script file is executed at this point
New test sequence directive in TDF:
· execute sql="DELETE FROM TPS;"
· The given SQL statement is executed at this point. However, no output is produced.
· New run directive parameter in TDF, to repeat the run execution a number
· of times: run repeats=
New parameter in ddf:
· ConnectionInit = "s...
Find us on Google+
