Hi, guys I'd like to get a little advice from you.
The following are three formats of printing performance tracing log file: [1] ----------------------------- Query Id: 2 - Start time: 2020-06-23 20:02:22.205 Query Id: 2 - Query Statement: select * from root Query Id: 2 - Number of series paths: 3 Query Id: 2 - Number of tsfiles: 2 Query Id: 2 - Number of sequence files: 2 Query Id: 2 - Number of unsequence files: 0 Query Id: 2 - Number of chunks: 3 Query Id: 2 - Average size of chunks: 4113 [2] ----------------------------- Query Id: 2 - Start time: 2020-06-23 19:38:35.109 | Query Statement: select * from root | Number of series paths: 3 Query Id: 2 - Number of tsfiles: 2 | Number of sequence files: 2 | Number of unsequence files: 0 Query Id: 2 - Number of chunks: 3 | Average size of chunks: 4113 [3] ----------------------------- Query Id: 2 - Start time: 2020-06-23 19:38:35.109, Query Statement: select * from root, Number of series paths: 3 Query Id: 2 - Number of tsfiles: 2, Number of sequence files: 2, Number of unsequence files: 0 Query Id: 2 - Number of chunks: 3, Average size of chunks: 4113 Which do you prefer? Any other suggestions are OK. Please leave your opinion. Xiangwei Wei <[email protected]> 于2020年6月23日周二 下午2:34写道： > Hi，Jialin > > Thank you for your explanation. > > Jialin Qiao <[email protected]> 于2020年6月23日周二 下午2:07写道： > >> Hi, >> >> > 4. the number of chunks, and average size of each chunk. >> >> Thanks, just an explanation, the average size of chunk is the average >> number of data points in each chunk. >> For now, the query performance highly depends on the number of chunks >> need to read. So measuring the chunk size is important for us to locate the >> problem. >> >> Bests, >> -- >> Jialin Qiao >> School of Software, Tsinghua University >> >> 乔嘉林 >> 清华大学 软件学院 >> >> > -----原始邮件----- >> > 发件人: "Xiangwei Wei" <[email protected]> >> > 发送时间: 2020-06-22 00:36:24 (星期一) >> > 收件人: [email protected] >> > 抄送: >> > 主题: I've submitted a PR for issue IOTDB-736 Query performance tracing >> > >> > Hi, all >> > I submitted a pr[1] to support [IOTDB-736] Query performance tracing[2]. >> > >> > I try to provide the performance tracing function by adding a >> performance >> > log and give a switch statement "Tracing on/off" to control whether to >> > print this log, which is off by default. >> > >> > The log records including: >> > >> > 1. the query sql, and the start time of this query >> > 2. the number of series paths >> > 3. the number of distinct tsfiles, including sequence and unsequence >> > 4. the number of chunks, and average size of each chunk. >> > >> > This pr concentrates on raw data query, it may modify something for >> > aggregation query and group by query later. >> > >> > >> > Please leave your opinions, thanks. >> > >> > [1] https://github.com/apache/incubator-iotdb/pull/1399 >> > [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-736 >> > >> > -- >> > Best, >> > Xiangwei Wei >> > > > -- > Best, > Xiangwei Wei > -- Best, Xiangwei Wei
