Skip to main content
Skip table of contents

General load, scaling and compression benchmarks

Load Tests

HAKOM TSM is able to read and store large amounts of data in relational databases with high performance.

BenchmarkSecondsThroughput rate (data point/ second)
Write (1.500 ZR x 30t x 24h x 2 = 2,16 M data points)11196.364
Read (25.000 ZR x 30t x 24h x 2 = 36 M data points)116310.345
Parallel-Reading(5 x 5.000 ZR x 30t x 24h x 2 = 5 x 7,2 M = 36 M data points)110327.273
Parallel-Writing (5 x 1.500 ZR x 30t x 24h x 2 = 5 x 2,16 M = 10,8 M data points)60180.000

Resources:

  • 1 PostgreSQL Server: 2 x Intel Xenon X5675 3.06 GHz, 8 GB RAM, Windows Server 2012
  • Application Server with 1 HAKOM Service: each 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10
  • 1 Client: 8 x Intel Xeon X5675 3.06 GHz, 16 GB RAM, Windows 10

Scaling-Tests

The following benchmarks show horizontal and vertical scaling effects with HAKOM TSM Services.

Data was written and read for 1,000 time series in 15-minute interval (96) over 31 days (2,976,000 values) using single and bulk requests. In the case of bulk requests, one bulk request was sent in parallel for every 100 time series, so that these tests also simulate simultaneous access by 10 users with 100 time series each. 

HAKOM Standard License vs. HAKOM Performance License (incl. service parallelization)

Standard vs. Performance column shows the percentage improvement of Performance License compared to Standard (1-Performance/Standard%).

Benchmark for (n=10)App ServerStandard PerformanceStandard vs. Performance
Write Singe-Request100:27,64900:10,95460,38%
Read Singe-Request100:08,62500:07,07817,94%
Write Bulk-Request100:35,10300:11,88566,14%
Read Bulk-Request100:07,12700:05,34425,02%
Write Bulk-Request200:26,33500:09,81162,75%
Read Bulk-Request200:05,62000:03,69534,25%

Resources:

  • 1 PostgreSQL Server: 2 x Intel Xenon X5675 3.06 GHz, 8 GB RAM, Windows Server 2012
  • 1 to 2 Application Server with 1 HAKOM Service: each 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10
  • 1 Client: 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10

Horizontal Scaling Effects with 1 to 4 App Servers

The following results were obtained with Performance License over 1 to 4 App Servers.

The Δ X vs. Y Server columns show the percentage improvement of X number of servers vs. Y number of servers.

Benchmark for (n=10)                 1 App Server

2 App Server

4 App Server

Δ 1 vs. 2 ServerΔ 2 vs. 4 ServerΔ 1 vs. 4 Server
Write Bulk-Request00:11,88500:09,94000:09,23216,37%7,12%22,32%
Read Bulk-Request00:05,34400:03,75700:02,90729,70%22,62%45,60%

Resources:

  • 1 PostgreSQL Server: 2 x Intel Xenon X5675 3.06 GHz, 8 GB RAM, Windows Server 2012
  • 1 to 4 Application Server with 1 HAKOM Service: each 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10
  • 1 Client: 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10

Horizontal and Vertical Scaling in Comparison

The following table compares scaling effects between the following constellations when reading 1,000 time series in 15 minute interval over 31 days:

  • 2 Engines with 8 Cores, 16 GB RAM and 2 HAKOM Services (2 x 8 Cores)
  • 1 Engine with 8 Cores, 16 GB RAM and 1 HAKOM Service (1 x 8 Cores)
  • 2 Engines with each 4 Cores, 8 GB RAM and each 1 HAKOM Service (2 x 4 Cores)
  • 1 Engine with 4 Cores, 8 GB RAM and 1 HAOM Service (1 x 4 Cores)
(x / y) x →2 x 8 Cores2 x 4 Cores1 x 8 Cores1 x 4 Cores
y ↓
00:02,24800:02,28600:02,69200:03,125
2 x 8 Cores00:02,248-101,69%119,75%139,01%
2 x 4 Cores00:02,28698,34%-117,76%136,70%
1 x 8 Cores00:02,69283,51%84,92%-116,08%
1 x 4 Cores00:03,12571,94%73,15%86,14%

Resources:

  • 1 PostgreSQL Server: 2 x Intel Xenon X5675 3.06 GHz, 8 GB RAM, Windows Server 2012
  • 1 to 4 Application Server with 1 HAKOM Service: each 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10
  • 1 Application Server with 1 up to  2 HAKOM Services: 8 x Intel Xeon X5675 3.06 GHz, 16 GB RAM, Windows 10
  • 1 Client: 2 x Intel Xeon X5675 3.06 GHz, 8 GB RAM, Windows 10

Compression Break-Even-Point

In HAKOM TSM time series values can be stored compressed. Thereby several values are stored in blocks with only one block timestamp, resulting in an significant reduction in the amount of data and database performance. Read more: Time Series Compression

The following evaluation shows from which % of the value changes of a compression block the performance becomes better with compression than without compression. 


Compressed25% of the block50% of the block75% of the block100% of the block
Write Bulk-Requestyes00:01,46900:01,60200:01,51900:01,454
Write Bulk-Requestno00:01,24800:01,42100:01,51400:01,632
Read Bulk-Requestyes00:00,87000:00,93200:00,93200:00,947
Read Bulk-Requestno00:00,87000:00,93200:00,93200:00,995
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.