This topic describes the results of TPC Benchmark™ H (TPC-H) benchmark tests for your reference.

Background information

The following tables describe the number of rows in each table and cluster specifications used for TPC-H benchmark tests.
  • Number of rows in each table
    Table name Number of rows
    LINEITEM 600,037,902
    ORDERS 150,000,000
    PARTSUPP 80,000,000
    PART 20,000,000
    CUSTOMER 15,000,000
    SUPPLIER 1,000,000
    NATION 25
    REGION 5
  • Cluster specifications
    Computing resource configuration Storage capacity Version Remarks
    64 compute units (CUs)

    (64 CPU cores and 256 GB of memory)

    100 GB r0.10.20 Uses the default configurations of the cluster. The number of shards is 40.
    128 CUs

    (128 CPU cores and 512 GB of memory)

    100 GB r0.10.20 Uses the default configurations of the cluster. The number of shards is 80.

Test result: import time in different scenarios

The import time indicates the amount of time required to import data to Hologres. The amount of time is measured in seconds. The following table describes the import time in different scenarios that provide 64 CUs of computing resources.

Note If you execute the COPY FROM STDIN statement to import data, data is imported from one file to the corresponding table in Hologres at a time. Concurrent import is unavailable.
Table name Number of rows Data volume Amount of time used to copy data to Hologres over the Internet Amount of time used to copy data to Hologres in a VPC Amount of time used to import data to Hologres by using a MaxCompute foreign table
LINEITEM 600,037,902 73.6 GB 3,070.453 694.364 148.165
ORDERS 150,000,000 16.4 GB 691.060 172.529 37.741
PARTSUPP 80,000,000 2.3 GB 468.560 107.092 18.488
PART 20,000,000 11.3 GB 96.342 24.020 8.083
CUSTOMER 15,000,000 2.3 GB 95.190 22.937 10.363
SUPPLIER 1,000,000 132 MB 5.057 1.803 1.503
NATION 25 2 KB 0.580 0.584 0.747
REGION 5 0.375 KB 0.168 0.153 0.430
Total 106 GB 4427.410 1023.482 225.52

Test result: import time presented in a bar chart

In the following bar chart, a blue bar indicates the amount of time used to copy data to Hologres over the Internet. A green bar indicates the amount of time used to copy data to Hologres in a virtual private cloud (VPC). A gray bar indicates the amount of time used to import data to Hologres by using a MaxCompute foreign table. A smaller y-axis value indicates a faster import speed.

Note The x-axis represents the table name and the y-axis the import time measured in seconds.

The following conclusions can be drawn based on the bar chart:

  • If you execute the COPY FROM STDIN statement to import data, the import time is affected by the bandwidth. The amount of time used to copy data to Hologres in a VPC is less than that used over the Internet.
  • The amount of time used to import data by using a MaxCompute foreign table is less than the amount of time used to import data by executing the COPY FROM STDIN statement.
Import time presented in a bar chart

Test result: execution time of each query in Hologres instances that use different computing resources

The amount of time used to query data in the internal tables of Hologres is measured in seconds. The following table describes the execution time of each query in Hologres instances that use different computing resources.

Query ID Hologres (64 CUs) Hologres (128 CUs)
1 1.99 1.23
2 0.61 0.43
3 1.58 0.72
4 1.18 0.51
5 2.65 1.95
6 0.17 0.11
7 1.65 0.77
8 2.43 1.29
9 5.49 2.66
10 1.65 0.62
11 0.36 0.32
12 1.15 0.63
13 1.55 0.75
14 0.27 0.19
15 0.26 0.20
16 1.05 0.89
17 1.18 0.52
18 11.52 1.83
19 1.00 0.70
20 1.10 1.08
21 3.83 2.37
22 0.94 0.46
Total 43.58 20.23

Test result: execution time of each query in Hologres presented in a bar chart

In the following bar chart, a blue bar indicates the amount of time used to query data in a Hologres instance that uses 64 CUs of computing resources. A green bar indicates the amount of time used to query data in a Hologres instance that uses 128 CUs of computing resources. A smaller y-axis value indicates a better performance of the instance in the TPC-H benchmark test. Higher specifications of the instance bring about a shorter execution time for each query.

Note The x-axis represents the query ID and the y-axis the execution time measured in seconds.
Execution time of each query in Hologres presented in a bar chart