Performance Metrics (Dynamic Test Data Reservation Service)

This section provides performance metrics for Dynamic (Model-Based) Test?Data Reservation Service.
tdm42
This section provides performance metrics for Dynamic (Model-Based) Test?Data Reservation Service.
2
2
Schema Distribution
The data is spread across three different databases: Oracle, Microsoft SQL Server, and DB2/AS400. The schema distribution is as follows:
Oracle
  • Orders (1 million records)
  • Shippers
  • Customers
Microsoft SQL Server
  • Categories
  • Employees
  • EmployeeTerritories
  • Order Details (10,000 records)
  • Region
  • Suppliers (10,000 records)
  • Territories
DB2/AS400 
  • Products (10,000 records)
  • CustomerCustomerDemo
The databases are distributed across different geographies with no optimization done on the databases. The following illustration shows how the application interacts with the databases. 
Performance_Metrics
Performance_Metrics
Performance result values are only indicative. Actual performance is dependent on several factors; for example, server configuration, network configuration, database configuration, and schema size.
Specifications
The following are the specifications:
  • Virtual machine (VM) on ESX
  • Microsoft Windows Server 2008 R2
  • 64-bit system
  • 2x Quad Core CPU
  • 8 GB RAM
  • Google Chrome 56.0.2924.87
  • 10 gbps virtual Ethernet network connection
Scenario 1: Test Data Model Including Only Orders Entity
This scenario includes a test data model that contains only the Orders entity. The following table shows the time that is taken to retrieve the specific result:
Requirement
Filter
Time Taken
Single filter on Orders
Get all orders for OrderDate=2016-12-30 00:00:00.0 or EmployeeID=2
Less than 3 seconds
Multiple filters on Orders
Get all orders for OrderDate=2016-12-30 00:00:00.0 , EmployeeID=2, and ShipVia=1
Less than 3 seconds
Return 10,000 orders based on a filter
Get all orders for ShipVia=1
Less than 3 seconds
Scenario 2: Test Data Model Including Orders and Order Details Entities
This scenario includes a test data model that contains Orders and Order Details entities. In this test data model, the Orders entity acts as a root entity and the OrderID field from Orders acts as a model key. The child entity Order Details is associated with the Orders entity. The following table shows the time that is taken to retrieve the specific result:
Requirement
Filter
Time Taken
Filter on Orders
Get all orders for EmployeeID=2
Less than 4 seconds
Filter on Order Details
Get all orders for TotalAmount=197.94
Less than 4 seconds
Filter on both Orders and Order Details
Get all orders for TotalAmount=197.94 and ShipRegion=WV
Less than 4 seconds
Scenario 3: Test Data Model Including Orders, Order Details, Products, and Suppliers Entities
This scenario includes a test data model that contains Orders, Order Details, Products, and Suppliers entities. In this test data model, the Orders entity acts as a root entity and the OrderID field from Orders acts as a model key. All other child entities are directly or indirectly (through associations with other entities) related to the Orders root entity. The following table shows the time that is taken to retrieve the specific result:
Requirement
Filter
Time Taken
Filter on Orders and other child entities
Get all orders for CompanyName=460LTD, Discount=52,  EmployeeID=2, ProductID=1, ShipVia=1, SupplierID=2, and UnitPrice=348 
Less than 4 seconds
Filter on child entities; however, no filter on Orders
Get all orders for CompanyName=460LTD, Discount=52,  ProductID=1, SupplierID=2, and UnitPrice=348
Less than 4 seconds
No filter on Orders, but multiple filters on child entities
Get all orders for CompanyName=460LTD, Discount=52,  ProductID=1, SupplierID=2, TotalAmount=197.94, and UnitPrice=348
Less than 4 seconds