Could you run jstack on the Kylin process and send out result? So that we can know what the query threads are blocked on. I encountered the same issue when doing load test, and found that most of query threads are blocked on class loading, and the class is code gen by calcite, so we may need calcite to fix it(Just a simple fix to change the generated class name). If you use Kylin 2.5 version, and most of your queries have similar pattern, you may try to use PreparedStatement, that may greatly increase the load performance. Kylin already support to cached preparedStatement parse result in Kylin server side since 2.5 (https://issues.apache.org/jira/browse/KYLIN-3434)
At 2018-09-20 14:30:56, "huaicui" <270922...@qq.com> wrote: >We use Kylin to design our project; But we have a problem: >A single query will be responded in 0.07 to 0.2 seconds. Following the >number of query concurrency, response time will be longer. When the number >of query concurrency is about 150, this value will be extended to 4 seconds >or more. Can you help me to fix this issue or give me some suggestion? > ><http://apache-kylin.74782.x6.nabble.com/file/t824/10.jpg> ><http://apache-kylin.74782.x6.nabble.com/file/t824/50.jpg> ><http://apache-kylin.74782.x6.nabble.com/file/t824/100.jpg> ><http://apache-kylin.74782.x6.nabble.com/file/t824/150.jpg> > >-- >Sent from: http://apache-kylin.74782.x6.nabble.com/
