Skip to content

Overview

Note: The Workload Services Framework is a benchmarking framework and is not intended to be used for the deployment of workloads in production environments. It is recommended that users consider any adjustments which may be necessary for the deployment of these workloads in a production environment including those necessary for implementing software best practices for workload scalability and security.

Introduction

HammerDB is the leading benchmarking and load testing software for the worlds most popular databases supporting Oracle Database, SQL Server, IBM Db2, MySQL, MariaDB and PostgreSQL.

This workload uses HammerDB to measure Database(s) performance natively. At this moment, this benchmarks measure performance of these databases :

  • Postgres on Centos9 and Windows
  • MySQL on Windows

Test Case

Below are the list of testcase(s) * test_aws_hammerdb_tpcc_native_windows2019_mysql8033 is running MySQL 8.0.33 on windows 2019 * test_aws_hammerdb_tpcc_native_centos9_postgresql14 is running Postgresql 14.12 on Centos7 * test_aws_hammerdb_tpcc_native_windows2016_postgresql14 is running Postgresql 14.12 on windows 2016 * test_aws_hammerdb_tpcc_native_windows2016_postgresql14_pkm is running Postgresql 14.12 on windows 2016

1 Prepare WSF environment

1.1 Download WSF repo
git clone https://github.com/intel/workload-services-framework.git mywsfrepo
cd mywsfrepo
1.2 Setup the development host

Setup the development host with setup-dev.sh. Document for this script. 

# in root folder of the repo: mywsfrepo/
cd script/setup
./setup-dev.sh
cd ../.. # back to root folder

1.3 Cmake configuration

You can use develop branch for workload evaluation . cmake options that may need your attention:

PLATFORM: SPR, ICX, EMR...check available options under cmake folder TERRAFORM_SUT: aws. TERRAFORM_OPTIONS: check available options under terraform options, common used options: general: --svrinfo publish: --intel_publish, --owner, --tags

1.3 Initialize Cloud accounts.

Please follow this document 

# in build folder of the repo: mywsfrepo/build
make aws           # or make -C ../.. aws, if under build/workload/<workload>
$ aws configure    # please specify a region and output format as json
$ exit

For now, you can continue to evaluate the workload.
#### 2 Evaluate the workload
##### 2.1 List available test cases with `ctest.sh`
```shell
# in build folder of the repo: mywsfrepo/build
./ctest.sh -N
# part of output:
#   Test #1: test_aws_hammerdb_tpcc_native_windows2019_mysql8033
#   Test #2: test_aws_hammerdb_tpcc_native_centos7_postgresql14
#   Test #3: test_aws_hammerdb_tpcc_native_windows2016_postgresql14
#   Test #4: test_aws_hammerdb_tpcc_native_windows2016_postgresql14_pkm
Simply run a testcase: 
./ctest.sh -R test_aws_hammerdb_tpcc_native_windows2016_postgresql14_pkm -VV --set AWS_DISK_SPEC_1_DISK_COUNT=1 --set AWS_DISK_SIZE=200 --set AWS_WORKER_OS_TYPE=windows2016 --set AWS_CLIENT_OS_TYPE=windows2016

KPI

Run the list-kpi.sh script to parse the KPIs from the validation logs.

The expected output will be similar to this. Please note that the numbers might be slightly different. 

# status: passed
New Orders Per Minute VU2 (orders/min): 82130
Transactions Per Minute VU2 (trans/min): 188754
Peak Num of Virtual Users: 2
*Peak New Orders Per Minute (orders/min): 82130
Peak Transactions Per Minute (trans/min): 188754

avg *Peak New Orders Per Minute (orders/min): 82130
std *Peak New Orders Per Minute (orders/min): 0
med *Peak New Orders Per Minute (orders/min): 82130
geo *Peak New Orders Per Minute (orders/min): 82130

Index Info

  • Name: HammerDB-TPCC-native
  • Category: DataServices
  • Platform: SPR, ICX
  • Keywords: POSTGRES, MYSQL
  • Permission: