Re: Performance Question

[Benjamin Kim]

Hi Todd,

I changed the key to be what you suggested, and I can’t tell the difference 
since it was already fast. But, I did get more numbers.

> 104M rows in Kudu table
- read: 8s
- count: 16s
- aggregate: 9s

The time to read took much longer from 0.2s to 8s, counts were the same 16s, 
and aggregate queries look longer from 6s to 9s.

I’m still impressed.

Cheers,
Ben 

> On Jun 15, 2016, at 12:47 AM, Todd Lipcon  wrote:
> 
> Hi Benjamin,
> 
> What workload are you using for benchmarks? Using spark or something more 
> custom? rdd or data frame or SQL, etc? Maybe you can share the schema and 
> some queries
> 
> Todd
> 
> Todd
> 
> On Jun 15, 2016 8:10 AM, "Benjamin Kim"  > wrote:
> Hi Todd,
> 
> Now that Kudu 0.9.0 is out. I have done some tests. Already, I am impressed. 
> Compared to HBase, read and write performance are better. Write performance 
> has the greatest improvement (> 4x), while read is > 1.5x. Albeit, these are 
> only preliminary tests. Do you know of a way to really do some conclusive 
> tests? I want to see if I can match your results on my 50 node cluster.
> 
> Thanks,
> Ben
> 
>> On May 30, 2016, at 10:33 AM, Todd Lipcon > > wrote:
>> 
>> On Sat, May 28, 2016 at 7:12 AM, Benjamin Kim > > wrote:
>> Todd,
>> 
>> It sounds like Kudu can possibly top or match those numbers put out by 
>> Aerospike. Do you have any performance statistics published or any 
>> instructions as to measure them myself as good way to test? In addition, 
>> this will be a test using Spark, so should I wait for Kudu version 0.9.0 
>> where support will be built in?
>> 
>> We don't have a lot of benchmarks published yet, especially on the write 
>> side. I've found that thorough cross-system benchmarks are very difficult to 
>> do fairly and accurately, and often times users end up misguided if they pay 
>> too much attention to them :) So, given a finite number of developers 
>> working on Kudu, I think we've tended to spend more time on the project 
>> itself and less time focusing on "competition". I'm sure there are use cases 
>> where Kudu will beat out Aerospike, and probably use cases where Aerospike 
>> will beat Kudu as well.
>> 
>> From my perspective, it would be great if you can share some details of your 
>> workload, especially if there are some areas you're finding Kudu lacking. 
>> Maybe we can spot some easy code changes we could make to improve 
>> performance, or suggest a tuning variable you could change.
>> 
>> -Todd
>> 
>> 
>>> On May 27, 2016, at 9:19 PM, Todd Lipcon >> > wrote:
>>> 
>>> On Fri, May 27, 2016 at 8:20 PM, Benjamin Kim >> > wrote:
>>> Hi Mike,
>>> 
>>> First of all, thanks for the link. It looks like an interesting read. I 
>>> checked that Aerospike is currently at version 3.8.2.3, and in the article, 
>>> they are evaluating version 3.5.4. The main thing that impressed me was 
>>> their claim that they can beat Cassandra and HBase by 8x for writing and 
>>> 25x for reading. Their big claim to fame is that Aerospike can write 1M 
>>> records per second with only 50 nodes. I wanted to see if this is real.
>>> 
>>> 1M records per second on 50 nodes is pretty doable by Kudu as well, 
>>> depending on the size of your records and the insertion order. I've been 
>>> playing with a ~70 node cluster recently and seen 1M+ writes/second 
>>> sustained, and bursting above 4M. These are 1KB rows with 11 columns, and 
>>> with pretty old HDD-only nodes. I think newer flash-based nodes could do 
>>> better.
>>>  
>>> 
>>> To answer your questions, we have a DMP with user profiles with many 
>>> attributes. We create segmentation information off of these attributes to 
>>> classify them. Then, we can target advertising appropriately for our sales 
>>> department. Much of the data processing is for applying models on all or if 
>>> not most of every profile’s attributes to find similarities (nearest 
>>> neighbor/clustering) over a large number of rows when batch processing or a 
>>> small subset of rows for quick online scoring. So, our use case is a 
>>> typical advanced analytics scenario. We have tried HBase, but it doesn’t 
>>> work well for these types of analytics.
>>> 
>>> I read, that Aerospike in the release notes, they did do many improvements 
>>> for batch and scan operations.
>>> 
>>> I wonder what your thoughts are for using Kudu for this.
>>> 
>>> Sounds like a good Kudu use case to me. I've heard great things about 
>>> Aerospike for the low latency random access portion, but I've also heard 
>>> that it's _very_ expensive, and not particularly suited to the columnar 
>>> scan workload. Lastly, I think the Apache license of Kudu is much more 
>>> appealing than the AGPL3 used by Aerospike. But, that's not really a 

Re: Kundera - JPA compliant Object Datastore Mapper for Kudu

[Jean-Daniel Cryans]

Cool, great to hear, Karthik :)

We do need some sort of roadmap on the website/wiki/or just as a list of
jiras with tags. Right now we've been mostly executing on this:
http://mail-archives.apache.org/mod_mbox/kudu-dev/201602.mbox/%3ccagptdncmbwwx8p+ygkzhfl2xcmktscu-rhlcqfsns1uvsbr...@mail.gmail.com%3E

We currently don't recommend running Kudu in production, so you won't find
many instances of it. This will change with 1.0 as described in the link
above. You can still find some companies using Kudu, for example Xiaomi's
use case is described from slide #13 in this deck:
http://www.slideshare.net/cloudera/apache-kudu-incubating-new-hadoop-storage-for-fast-analytics-on-fast-data-by-todd-lipcon-software-engineer-cloudera-kudu-founder

As for insights on using Kudu with Object Mappers, you tell me :) I think
one thing missing that'll make it even more powerful would be to have
nested types support in Kudu. There's a jira for it but no one's working on
it: https://issues.apache.org/jira/browse/KUDU-1261

Cheers,

J-D

On Thu, Jun 30, 2016 at 1:48 AM, Karthik Prasad Manchala <
karthikp.manch...@impetus.co.in> wrote:

> Hi J-D,
>
>
> I have positive feedback on Kudu's API. I can say it is one of the easiest
> APIs I have used till date.
>
>
> There are no such weird things that I noticed but I did not come across
> any road map of Kudu for the features to be planned. It would be
> amazing to know.
>
>
> Also, I was wondering if you could share any instances where Kudu is being
> used in production? And some insights on using Kudu with an Object
> Mapper tool like Kundera?
>
>
> Thanks,
>
> Karthik.
> --
> *From:* Jean-Daniel Cryans 
> *Sent:* 29 June 2016 22:40
> *To:* user@kudu.incubator.apache.org
> *Subject:* Re: Kundera - JPA compliant Object Datastore Mapper for Kudu
>
> Hi Karthik!
>
> Thanks for sharing this.
>
> I see that you've written most of the code so I wonder, do you have any
> feedback on Kudu's APIs? Any weird things you noticed? Any gotchas?
>
> We're getting close to 1.0, so we still have some time to make
> (potentially breaking) changes.
>
> Thanks!
>
> J-D
>
> On Wed, Jun 29, 2016 at 3:48 AM, Karthik Prasad Manchala <
> karthikp.manch...@impetus.co.in> wrote:
>
>> Hi all,
>>
>>
>> Kundera  being one of the
>> most popular JPA provider for NoSql datastores has added support for basic
>> CRUD operations and Select queries on Kudu. Please feel free to explore
>> more using the below link.
>>
>>
>> - https://github.com/impetus-opensource/Kundera/wiki/Kundera-with-Kudu
>>
>>
>> Thanks and regards,
>>
>> Team Kundera.
>>
>> --
>>
>>
>>
>>
>>
>>
>> NOTE: This message may contain information that is confidential,
>> proprietary, privileged or otherwise protected by law. The message is
>> intended solely for the named addressee. If received in error, please
>> destroy and notify the sender. Any use of this email is prohibited when
>> received in error. Impetus does not represent, warrant and/or guarantee,
>> that the integrity of this communication has been maintained nor that the
>> communication is free of errors, virus, interception or interference.
>>
>
>
> --
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>