Hello, Usually, if the cube has been well designed and tunned, one Kylin server can support 50 to 150 QPS. From the Cisco team's experience, with enabling some advanced features like query cache and prepared statement, one Kylin server can support up to 500 QPS:
https://kylin.apache.org/blog/2019/01/17/cisco-throughput-5x/ If your QPS is not ideal, please try to tune a single query's performance and optimize the cube design. Best regards, Shaofeng Shi 史少锋 Apache Kylin PMC Email: [email protected] Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: [email protected] Join Kylin dev mail group: [email protected] [email protected] <[email protected]> 于2019年8月26日周一 下午4:32写道： > > Hi: > According to kylin's introduction, an ordinary server can accept tens > to hundreds of QPS. However, I found in the actual production that the QPS > of a query node can only reach single digits. It is reasonable to say that > the concurrency of a SpringBoot project is relatively high, and the > resolution speed of Calcite does not stop there.HBase's reading speed is no > problem. But the actual effect is so abnormal, what could be the problem? > > ------------------------------ > [email protected] > >
