Databases 7 min read

How a Chinese Startup Cracked the 12‑Year TPC‑DS Benchmark: Inside the Database Performance Breakthrough

A Chinese company, StarRing Technology, became the first ever to pass the notoriously difficult TPC‑DS benchmark, revealing the test’s history, methodology, and why this achievement marks a major milestone for database performance in the big‑data era.

ITPUB
ITPUB
ITPUB
How a Chinese Startup Cracked the 12‑Year TPC‑DS Benchmark: Inside the Database Performance Breakthrough

What is TPC‑DS?

The Transaction Processing Performance Council (TPC) defines standardized benchmarks for data‑management systems. TPC‑DS, introduced in 2006, measures analytical query performance using 99 distinct queries executed against a multi‑step workload.

Benchmark workflow (six steps)

Data Load Test (LD)

Power Test (PT) – run 99 queries in a single stream

Throughput Test 1 (TT1) – run 99 queries across multiple streams

Maintenance Test 1 (DM1) – refresh the database

Throughput Test 2 (TT2) – re‑run 99 queries across multiple streams

Maintenance Test 2 (DM2) – refresh the database again

The queries are generated from templates by the dsqgen tool using a seed value, so parameter values are unknown before execution. Query order varies across streams. Typical data volumes start at 10 TB.

Test environment

The benchmark was executed on a Cisco UCS integrated infrastructure combined with Transwarp Data Hub v5.1. The software stack included StarRing’s distributed graph database StellarDB , flash‑storage database ArgoDB , and the TDH 6.0 big‑data platform.

Official results are published at: http://www.tpc.org/tpcds/results/tpcds_advanced_sort.asp

Why TPC‑DS is difficult

Successful completion requires full SQL compliance, robust transaction support, and scalable execution under massive data‑exchange loads. Traditional RDBMS vendors (e.g., IBM, Oracle, Teradata) have struggled with node‑level bottlenecks at the required scale, often resorting to specialized hardware. Hadoop‑based platforms (e.g., Cloudera, Hortonworks, Databricks) are limited by architectural constraints that prevent execution of the complete benchmark suite.

StarRing testing timeline

StarRing began the first phase (Data Load Test) in late 2014. The remaining five steps were completed over the next three years. Results were submitted to TPC in July of the prior year and underwent a five‑month audit before public release.

Implications

Passing TPC‑DS demonstrates that StarRing’s platform can achieve performance comparable to, or exceeding, leading foreign vendors in large‑scale analytical workloads, providing a new reference point for evaluating high‑performance data‑analytics systems.

Benchmark result chart
Benchmark result chart
TPC‑DS query execution order
TPC‑DS query execution order
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Big DataPerformance TestingbenchmarkdatabasesTPC-DS
ITPUB
Written by

ITPUB

Official ITPUB account sharing technical insights, community news, and exciting events.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.