You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Julian Feinauer (Jira)" <ji...@apache.org> on 2020/06/03 11:07:00 UTC

[jira] [Commented] (IOTDB-736) Query performance tracing

    [ https://issues.apache.org/jira/browse/IOTDB-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124862#comment-17124862 ] 

Julian Feinauer commented on IOTDB-736:
---------------------------------------

I would, at least partially, include that in IOTDB-23. At least for metrics to get metrics about query durations.
How does tracing on work exactly in Cassandra? Does it have a separate log with timing informations?

> Query performance tracing
> -------------------------
>
>                 Key: IOTDB-736
>                 URL: https://issues.apache.org/jira/browse/IOTDB-736
>             Project: Apache IoTDB
>          Issue Type: New Feature
>          Components: Core/Engine
>            Reporter: Xiangdong Huang
>            Priority: Major
>
> Hi,
> Today I run a `select count(s1) from root.some_time_series`, while there is no un-sequence data. The data type is text and  there is 1.5TB data totally and the time series has about 15GB data, then it spends 17s.
>  
> is that possible to trace the query process for debugging the performance?
> Like what Cassandra provides, `tracing on`, and then how many sstables or tombstone are read and the time cost is clear.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)