TPC-W is a transactional web e-Commerce benchmark, introduced by the Transaction Processing Performance Council. TPC-W specifies an e-Commerce workload that simulates the activities of a retail website which produces heavy load on the backend database.
Users of the TPC-W benchmark can browse and order products from the website. In the case of TPC-W the products are books. The expected introduction or Home page is the first page user will see. It includes the company logo, promotional items and navigation options to the top best selling books, a list of new books, search pages, client's shopping cart, and order status pages. User can browse pages containing a list of new or best selling books grouped by subject, or perform searches against all books based upon a title, author or subject. A product page will give you detailed information for the book along with a picture of the book's front cover. User may order books by entering the order web pages. If user is a new customer s/he will have to fill out a customer registration page while for returning customers their information will be retrieved from the database and filled in automatically for them. User can change the quantity of the order or delete a book from the shopping cart. When user wishes to buy, s/he enters credit card information and submits the order. The system will obtain credit card authorization from a Payment Gateway Emulator (PGE), and present the user with an order confirmation page. At a later date user can view the status of his/her last order. Two additional web pages are provided for the system administrator to change book's front cover picture and price. This change is reflected in the new product book list. Essentially, the TPC-W benchmark provides basic functionality required of an Internet e-Commerce website.
TPC-W benchmark specifies the application database schema, the set of 14 web interactions (web pages), and how their execution manipulates application data. It also specifies data consistency and transactional requirements, database scaling and population, and various other aspects, e.g., which web interactions must be covered by SSL. However, TPC-W neither provides sample implementation of the application, nor it prescribes any implementation methodic or limits it to a specific technology. Besides the application structure, TPC-W specifies all aspects of the workload profile, performance metrics of interest, and required structure of the official disclosure report.
In Parallel and Distributed Systems Research Group (PDSG) at New York University, we have implemented TPC-W benchmark as a J2EE component-based application (TPC-W-NYU). The main features of the application are:
You may also find all the documentation in the "docs" directory of the ZIP distributon package.
Back to the Home Page of Alexander Totok
Back to the PDSG Home Page
Last update: Sunday, November 20, 2005.