Hello all : +1 The binary distribution: version number in CLI [ok] start in CentOS7, jdk11 [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 3C5D) (500 in 3C5D) SENSOR_NUMBER=500 BATCH_SIZE_PER_WRITE=100 LOOP=10000 ///////////////////////////////////////////////////////////////////////////
////////////////////////////### Test Result ###//////////////////////////// 3C3D: Timeseries Num : 25,000；Loaded 25,000,000,000points； Non-Aligned Timseries: Throughput(points/s): 15,371,100 Cost Time(s):1,678 Latency(ms): Avg 27.52, Min 3.83, MiddleAvg 5.04, Max 23,582.6 Aligned Timseries: Throughput(points/s): 23,016,100 Cost Time(s):1,119 Latency(ms): Avg 17.92, Min 3.41, MiddleAvg 4.17, Max 15,849.5 3C5D:Timeseries Num : 250,000；Loaded 250,000,000,000points； Non-Aligned Timseries: Throughput(points/s):46,091,600 Cost Time(s):5,477 Latency(ms): Avg 9.84, Min 3.53, MiddleAvg 5.1, Max 5,409.47 Aligned Timseries: Throughput(points/s):46,229,700 Cost Time(s):5,456 Latency(ms): Avg 9.5, Min 3.2, MiddleAvg 4.61, Max 5,389.18 /////////////////////////////////////////////////////////////////////////// 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<mailto:hao...@apache.org> 发送时间: 2023年12月27日 12:33 收件人: dev@iotdb.apache.org<mailto:dev@iotdb.apache.org> 主题: [VOTE] Apache IoTDB 1.3.0 RC1 release Hi all, Apache IoTDB 1.3.0 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: v1.3.0 Hash for the release tag: fe787cac2ddd874b44482a80306d9d6ae333143c 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] You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1154 [2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release [5] https://github.com/apache/iotdb/blob/v1.3.0/RELEASE_NOTES.md [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS Best, Haonan Hou
