kylin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: Re: Apache Kylin versus Cloudera Impala
Date Thu, 28 May 2015 03:08:15 GMT
Hi , Luke

Thanks for your prompt advice. 

Yeah, the pre-calculation cube is an obvious advantage for OLAP engine. However, cube build

may need to be leveraged over runtime scan / aggregation. We are expecting the performance

between Kylin and MPP sql engine like Impala, and we are just about to do that. Would share

valuable information AFAIK.
From: Luke Han
Date: 2015-05-28 10:30
Subject: Re: Apache Kylin versus Cloudera Impala
Hi Sun,
    There's no benchmark from our side yet,especially in prod env. I'm also
very curious to know if someone did such comparison.
    The direct advantage for Kylin over Impala (include other MPP solution):
    1. Non-Invasive Design: you do not need to install any agent, library
or others in your existing Hadoop Cluster (Neither on Namenode or DataNode)
    2. Pre-Calculation result avoid runtime scan/aggregation, that mean you
could get result more faster in seconds latency over billions data.
Best Regards!
Luke Han
2015-05-28 10:20 GMT+08:00 <>:
> Hi, team
> Really interested in the performance comparison and also the native design
> advantage over Apache Kylin
> and Cloudera Impala. As the official saying, Cloudera Impala is a
> "Lightning-fast, distributed SQL queries
> for petabytes of data stored in Apache Hadoop clusters". Kylin can goes to
> 10-1000x query efficiency over
> hive in the usage of MOLAP,  while Cloudera Impala can also achieve much
> more performance upgrade over
> hive.
> Question is : Does Kylin do some benchmark test or performance comparison
> with Cloudera Impala in production
> environment? What can be the direct advantage for Apache Kylin over
> Cloudera Impala?
> If anyone had deployed and used both products in your usage, please kindly
> share any available suggestions.
> Best regards,
> Sun.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message