Hi,
1. I will present this tool soon, which has taken most of my time recently. 2. I guess so, but I could not find a good way to verify it. I am using 10240 as the chunk size limit, so there is a good chance that every chunk contains more points are the compressor works better. 3. With the help of most mail clients, I believe this is easy. If you are asking for any recommendations, the one from NetEase would be fine. | | Tian Jiang | | jt2594...@163.com | 签名由网易邮箱大师定制 On 9/2/2019 23:21，Xiangdong Huang<saint...@gmail.com> wrote： Hi Tianjiang, 1. I really like the "merge (statistics)", can it be a tool/remote call of IoTDB? 2. the data size is reduced from "32G + 9.3G" to "26G". Is that because the compression is improved or the chunks (and their metadata) are reduced? (If the latter, what the threshold of the number of data points in a chunk for merging is?) 3. why you can attach a file on the mail list... Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Tian Jiang <jt2594...@163.com> 于2019年9月2日周一 上午2:15写道： Hi, I have done a simple experiment comparing enabling merge or not and here are some basic conclusions: 1. Compared with disabling merge, enabling merge does not affect insertion significantly. 2. After merges are done, cold cache query (performed on a newly rebooted IoTDB) is significantly improved. 3. After merges are done, hot cache query (performed on a already queried IoTDB) is not affected. 4. With background insertions, merges can be very slow and without them, merges are a little faster than insertions. 5. When merges are done, the total size of data files reduces significantly. For detailed experiment results, please see the attachment. Tian Jiang
