Hello  all :

+1



Download ‘apache-iotdb-2.0.2-all-bin.zip’ from the link [ok]

Check the binary distribution:

Start ConfigNode, DataNode with JDK17 on CentOS7 [ok]

Version number in CLI [ok]

Performance verification [ok]

////////////////////////////### Server Configurations ###//////////////////

CPU=16

Memory=32G

Disk=1.8T HDD

Ethernet=1000Mbit

///////////////////////////////////////////////////////////////////////////

////////////////////////////### IoTDB Configurations ###///////////////////

MAX_HEAP_SIZE="20G" in datanode-env.sh

MAX_HEAP_SIZE="6G" in confignode-env.sh

schema_replication_factor=3

data_replication_factor=3

all_compaction=false

///////////////////////////////////////////////////////////////////////////

////////////////////////////### Client Mode ###////////////////////////////

Insert Non-Aligned/Aligned timeseries with SESSION_BY_TABLET

CLIENT_NUMBER=10

GROUP_NUMBER=10

DEVICE_NUMBER=(50 in 3C3D) (500 in 3C5D)

SENSOR_NUMBER=500

BATCH_SIZE_PER_WRITE=100

LOOP=(20000 in 3C3D) (10000in 3C5D)

///////////////////////////////////////////////////////////////////////////



////////////////////////////### Test Result ###////////////////////////////

3C3D: Timeseries Num : 25,000;Loaded 50,000,000,000points;

Non-Aligned Timseries:

Throughput(points/s): 48,107,800  Cost Time(s):1,054

Latency(ms): Avg 9.47, Min 4.89, MiddleAvg 7.48, Max 1,093.57

Aligned Timseries:

Throughput(points/s): 56,606,600 Cost Time(s):899

Latency(ms): Avg 8.01, Min 4.52, MiddleAvg 6.03, Max 893.22
Table Mode:

Throughput(points/s): 53,597,500  Cost Time(s):942

Latency(ms): Avg 8.18, Min 4.52, MiddleAvg 6.03, Max 6,394.69




3C5D:Timeseries Num : 250,000;Loaded 250,000,000,000points;

Non-Aligned Timseries:

Throughput(points/s): 59,823,300  Cost Time(s):4,195

Latency(ms): Avg 7.69, Min 4.28, MiddleAvg 6.13, Max 1,114.81

Aligned Timseries:

Throughput(points/s): 64,593,700  Cost Time(s):3,889

Latency(ms): Avg 7.08, Min 3.63, MiddleAvg 5.55, Max 1,107.85
Table Mode:

Throughput(points/s): 65,611,500  Cost Time(s):3,819

Latency(ms): Avg 6.9, Min 3.61, MiddleAvg 5.32, Max 13,889.1


///////////////////////////////////////////////////////////////////////////





Avg: Average time cost of all ingestion operations. [ms]

MiddleAvg: Average time cost of ingestion operations without 5% head and tail. 
[ms]

Min: Min single operation time cost of all ingestion operations. [ms]

Max: Max single operation  time cost of all ingestion operations. [ms]

There results are tested with 
iot-benchmark(https://github.com/thulab/iot-benchmark)

That’s all.

Please feel free to contact me if you have any questions

Thank you.

Best Reagrds!

Qingxin Feng

________________________________
发件人: Haonan Hou <hao...@apache.org>
发送时间: 2025年4月14日 23:04
收件人: dev@iotdb.apache.org <dev@iotdb.apache.org>
主题: [VOTE] Apache IoTDB 2.0.2 RC1 release

Hi all,

Apache IoTDB 2.0.2 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v2.0.2
Hash for the release tag: db893017926090854b0199f237a1ff5911407556

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

[ ] +1 accept (indicate what you validated)
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1164
[2] https://dist.apache.org/repos/dist/dev/iotdb/2.0.2/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://dist.apache.org/repos/dist/dev/iotdb/2.0.2/rc1/RELEASE_NOTES.md
[5] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Reply via email to