Brokers are being offered a new database transaction processing standard to test their existing systems against.
The Transaction Processing Performance Council (TPC) has approved and is now promoting the new Benchmark E (TPC-E) standard.
TPC-E is a new On-Line Transaction Processing (OLTP) workload standard developed by the TPC.
The new standard replaces the outdated TPC-C standard, which does not fully account for the way servers and databases now interact with each other, since processors have become ever more powerful and storage technology has changed.
The TPC-E benchmark simulates the OLTP workload of a brokerage firm. The focus of the benchmark is the central database that executes transactions related to the firm’s customer accounts.
Although the underlying business model of TPC-E is a brokerage firm, the database schema, data population, transactions, and implementation rules have been designed to be broadly representative of most modern OLTP systems.
EGen is a TPC provided software package designed to facilitate the implementation of TPC-E.
EGen provides consistent data generation independent of the underlying environment, transaction and frame flow control management, project build and make file templates.
The TPC-E benchmark uses a database to model a brokerage firm with customers who generate transactions related to trades, account inquiries, and market research.
The brokerage firm in turn interacts with financial markets to execute orders on behalf of the customers and updates relevant account information.
The benchmark is “scalable,” meaning that the number of customers defined for the brokerage firm can be varied to represent the workloads of different-size businesses.
The benchmark defines the required mix of transactions the benchmark must maintain. The TPC-E metric is given in transactions per second (tps). It specifically refers to the number of trade-result transactions the server can sustain over a period of time.
More details on pricing of the new testing system are available at:
Comment on this article: firstname.lastname@example.org