Re: scylladb

On Tue, Mar 14, 2017 at 7:43 AM, Eric Evans wrote: > On Sun, Mar 12, 2017 at 4:01 PM, James Carman > wrote: > > Does all of this Scylla talk really even belong on the Cassandra user > > mailing list in the first place? > > I personally

Re: scylladb

On Sun, Mar 12, 2017 at 4:01 PM, James Carman wrote: > Does all of this Scylla talk really even belong on the Cassandra user > mailing list in the first place? I personally found it interesting, informative, and on-topic when it was about justification of the 10x

Re: scylladb

On Mon, Mar 13, 2017 at 12:17 AM, benjamin roth wrote: > @Dor,Jeff: > > I think Jeff pointed out an important fact: You cannot stop CS, swap > binaries and start Scylla. To be honest that was AFAIR the only "Oooh :(" I > had when reading the Scylla "marketing material". > If

Re: scylladb

Hi, We did indeed consider support for a mixed cluster, but in the end decided against it, for many reasons: - the internode protocol is underdocumented and keeps changing, so it would be hard to support it, and hard to test it - it would limit the kind of optimizations we can do by

Re: scylladb

We came to the thread to provide technical answers about whether the difference in performance arise from C++ only or beyond. When the discussion included numa, we even dove deep into the weeds. I think we provided enough answers and I respect all of the opinions here and thus if someone has

Re: scylladb

@Dor,Jeff: I think Jeff pointed out an important fact: You cannot stop CS, swap binaries and start Scylla. To be honest that was AFAIR the only "Oooh :(" I had when reading the Scylla "marketing material". If that worked it would be very valuable from both Scylla's and a users' point of view. As

Re: scylladb

I don't think ScyallDB guys started this conversation in the first place to suggest or promote "drop-in replacement". It was something that is brought up by one of the Cassandra users and ScyallDB guys just clarified it. They are gracious enough to share the internals in detail. honestly, I find

Re: scylladb

On 2017-03-12 14:29 (-0700), James Carman wrote: > Well, looking back, it appears this thread is from 2015, so apparently > everyone is okay with it. > > Promoting a value-add product that makes using Cassandra easier/more > efficient/etc would be cool, but coming

Re: scylladb

Well, looking back, it appears this thread is from 2015, so apparently everyone is okay with it. Promoting a value-add product that makes using Cassandra easier/more efficient/etc would be cool, but coming to the Cassandra mailing list to promote a "drop-in replacement" (use us, not Cassandra)

Re: scylladb

yes. On Sun, Mar 12, 2017 at 2:01 PM, James Carman wrote: > Does all of this Scylla talk really even belong on the Cassandra user > mailing list in the first place? > > > > > On Sun, Mar 12, 2017 at 4:07 PM Jeff Jirsa wrote: > > > > On 2017-03-11

Re: scylladb

Does all of this Scylla talk really even belong on the Cassandra user mailing list in the first place? On Sun, Mar 12, 2017 at 4:07 PM Jeff Jirsa wrote: On 2017-03-11 22:33 (-0700), Dor Laor wrote: > On Sat, Mar 11, 2017 at 10:02 PM, Jeff Jirsa

Re: scylladb

On Sun, Mar 12, 2017 at 3:45 PM, Dor Laor wrote: > On Sun, Mar 12, 2017 at 12:11 PM, Edward Capriolo > wrote: > >> The simple claim that "Scylla IS a drop in replacement for C*" shows >> that they clearly don't know as much as they think they do. >> >>

Re: scylladb

On 2017-03-11 22:33 (-0700), Dor Laor wrote: > On Sat, Mar 11, 2017 at 10:02 PM, Jeff Jirsa wrote: > > On 2017-03-10 09:57 (-0800), Rakesh Kumar wrote: > > > Cassanda vs Scylla is a valid comparison because they both are > > compatible. Scylla is a drop-in

Re: scylladb

On Sun, Mar 12, 2017 at 12:11 PM, Edward Capriolo wrote: > The simple claim that "Scylla IS a drop in replacement for C*" shows that > they clearly don't know as much as they think they do. > > Even if it did supposedly "support everything" it would not actually work >

Re: scylladb

The simple claim that "Scylla IS a drop in replacement for C*" shows that they clearly don't know as much as they think they do. Even if it did supposedly "support everything" it would not actually work like that. For example, some things in Cassandra work "the way they work" . They are not

Re: scylladb

On Sun, Mar 12, 2017 at 11:15 AM, Jonathan Haddad wrote: > I don't think Jeff comes across as angry. He's simply pointing out that > ScyllaDB isn't a drop in > Agree, I take it back, it's wasn't due to this. > replacement for Cassandra. Saying that it is is very

Re: scylladb

optimization and keep crushing it. >>> >>> P.S., I don't work for ScyllaDB. >>> >>> On Thu, Mar 9, 2017 at 6:02 PM, Rakesh Kumar <rakeshkumar...@outlook.com >>> > wrote: >>> >>>> In all of their presentation they keep harping on

Re: scylladb

I don't think Jeff comes across as angry. He's simply pointing out that ScyllaDB isn't a drop in replacement for Cassandra. Saying that it is is very misleading. The marketing material should really say something like "drop in replacement for some workloads" or "aims to be a drop in

RE: scylladb

From: sfesc...@gmail.com [mailto:sfesc...@gmail.com] Sent: dimanche 12 mars 2017 09:23 To: user@cassandra.apache.org Subject: Re: scylladb On Sat, Mar 11, 2017 at 1:52 AM Avi Kivity <a...@scylladb.com<mailto:a...@scylladb.com>> wrote: Lastly, why don't you test Scylla yourself? It's

Re: scylladb

On Sat, Mar 11, 2017 at 1:52 AM Avi Kivity wrote: > > > Lastly, why don't you test Scylla yourself? It's pretty easy to set up, > there's nothing to tune. > > Avi > I'll look seriously at Scylla when it is 3.0.12 compatible.

Re: scylladb

On Sun, Mar 12, 2017 at 11:40 AM, Edward Capriolo wrote: > > > On Sun, Mar 12, 2017 at 1:38 AM, benjamin roth wrote: > >> There is no reason to be angry. This is progress. This is the circle of >> live. >> >> It happens anywhere at any time. >> >> Am

Re: scylladb

On Sun, Mar 12, 2017 at 1:38 AM, benjamin roth wrote: > There is no reason to be angry. This is progress. This is the circle of > live. > > It happens anywhere at any time. > > Am 12.03.2017 07:34 schrieb "Dor Laor" : > >> On Sat, Mar 11, 2017 at 10:02 PM,

Re: scylladb

; >> In all of their presentation they keep harping on the >> fact that scylladb is written in C++ and does not carry >> the overhead of Java. Still the difference looks staggering. >> >

Re: scylladb

One more thing. Pretty much every database that is written in C++ or Java uses native kernel threads for non-blocking I/O as well. They didn't use Seaster or Quasar but anyways I am going to read up on Seaster and see what it really does. On Sun, Mar 12, 2017 at 3:48 AM, Kant Kodali

Re: scylladb

Sorry I made some typo's here is a better version. @Avi "User-level scheduling is great for high performance I/O intensive applications like databases and file systems." This is generally a claim made by people who want to use user-level threads but I rarely had seen any significant performance

Re: scylladb

> If you have thread-per-core and N (logical) cores, and have M tasks > running concurrently where M > N, then you need a scheduler to decide which > of those M tasks gets to run on those N kernel threads. Whether those M > tasks are user-level threads, or callbacks, or a mix of the two is >

Re: scylladb

If you have thread-per-core and N (logical) cores, and have M tasks running concurrently where M > N, then you need a scheduler to decide which of those M tasks gets to run on those N kernel threads. Whether those M tasks are user-level threads, or callbacks, or a mix of the two is

Re: scylladb

@Avi I don't disagree with thread per core design and in fact I said that is a reasonable/good choice. But I am having a hard time seeing through how user level scheduling can make a significant difference even in Non-blocking I/O case. My question really is that if you already have TPC why do

Re: scylladb

We already quantified it, the result is Scylla. Now, Scylla's performance is only in part due to the threading model, so I can't give you a number that quantifies how much just this aspect of the design is worth. Removing it (or adding it to Cassandra) is a multi-man-year effort that I can't

Re: scylladb

On Sun, Mar 12, 2017 at 12:23 AM, Avi Kivity wrote: > > > On 03/12/2017 12:19 AM, Kant Kodali wrote: > > My response is inline. > > On Sat, Mar 11, 2017 at 1:43 PM, Avi Kivity wrote: > >> There are several issues at play here. >> >> First, a database runs a

Re: scylladb

​ On Sun, Mar 12, 2017 at 2:42 PM, Bhuvan Rawal wrote: > Looking at the costs of cloud instances, it clearly appears the cost of > CPU dictates the overall cost of the instance. Having 2X more cores > increases cost by nearly 2X keeping other things same as can be seen

Re: scylladb

Looking at the costs of cloud instances, it clearly appears the cost of CPU dictates the overall cost of the instance. Having 2X more cores increases cost by nearly 2X keeping other things same as can be seen below as an example: (C3 may have slightly better processor but not more than 10-15%

Re: scylladb

@Avi "User-level scheduling is great for high performance I/O intensive applications like databases and file systems." This is generally a claim made by people you want to use user-level threads but I rarely had seen any significant performance gain. Since you are claiming that you do. It would

Re: scylladb

btw, for an example of how user-level tasks can be scheduled in a way that cannot be done with kernel threads, see this pair of blog posts: http://www.scylladb.com/2016/04/14/io-scheduler-1/ http://www.scylladb.com/2016/04/29/io-scheduler-2/ There's simply no way to get this kind of

Re: scylladb

On 03/12/2017 12:19 AM, Kant Kodali wrote: My response is inline. On Sat, Mar 11, 2017 at 1:43 PM, Avi Kivity > wrote: There are several issues at play here. First, a database runs a large number of concurrent operations, each of

Re: scylladb

On Sat, Mar 11, 2017 at 2:19 PM, Kant Kodali wrote: > My response is inline. > > On Sat, Mar 11, 2017 at 1:43 PM, Avi Kivity wrote: > >> There are several issues at play here. >> >> First, a database runs a large number of concurrent operations, each of >>

Re: scylladb

There is no reason to be angry. This is progress. This is the circle of live. It happens anywhere at any time. Am 12.03.2017 07:34 schrieb "Dor Laor" : > On Sat, Mar 11, 2017 at 10:02 PM, Jeff Jirsa wrote: > >> >> >> On 2017-03-10 09:57 (-0800), Rakesh

Re: scylladb

On Sat, Mar 11, 2017 at 10:02 PM, Jeff Jirsa wrote: > > > On 2017-03-10 09:57 (-0800), Rakesh Kumar wrote: > > Cassanda vs Scylla is a valid comparison because they both are > compatible. Scylla is a drop-in replacement for Cassandra. > > No, they aren't, and no, it isn't >

Re: scylladb

Why? Am 12.03.2017 07:02 schrieb "Jeff Jirsa" : > > > On 2017-03-10 09:57 (-0800), Rakesh Kumar wrote: > > Cassanda vs Scylla is a valid comparison because they both are > compatible. Scylla is a drop-in replacement for Cassandra. > > No, they aren't, and no, it isn't > > > > >

Re: scylladb

On 2017-03-10 09:57 (-0800), Rakesh Kumar wrote: > Cassanda vs Scylla is a valid comparison because they both are compatible. > Scylla is a drop-in replacement for Cassandra. No, they aren't, and no, it isn't

Re: scylladb

ou can >>>> expect them to continue on with their optimization and keep crushing it. >>>> >>>> P.S., I don't work for ScyllaDB. >>>> >>>> On Thu, Mar 9, 2017 at 6:02 PM, Rakesh Kumar < >>>> rakeshkumar...@outlook.com> wrote:

Re: scylladb

rk for ScyllaDB. >>> >>> On Thu, Mar 9, 2017 at 6:02 PM, Rakesh Kumar <rakeshkumar...@outlook.com >>> > wrote: >>> >>>> In all of their presentation they keep harping on the fact that >>>> scylladb is written in C++ and does not carr

Re: scylladb

My response is inline. On Sat, Mar 11, 2017 at 1:43 PM, Avi Kivity wrote: > There are several issues at play here. > > First, a database runs a large number of concurrent operations, each of > which only consumes a small amount of CPU. The high concurrency is need to > hide

Re: scylladb

There are several issues at play here. First, a database runs a large number of concurrent operations, each of which only consumes a small amount of CPU. The high concurrency is need to hide latency: disk latency, or the latency of contacting a remote node. This means that the scheduler will

Re: scylladb

Here is the Java version http://docs.paralleluniverse.co/quasar/ but I still don't see how user level scheduling can be beneficial (This is a well debated problem)? How can this add to the performance? or say why is user level scheduling necessary Given the Thread per core design and the callback

Re: scylladb

Scylla uses a the seastar framework, which provides for both user-level thread scheduling and simple run-to-completion tasks. Huge pages are limited to 2MB (and 1GB, but these aren't available as transparent hugepages). On 03/11/2017 10:26 PM, Kant Kodali wrote: @Dor 1) You guys have a CPU

Re: scylladb

@Dor 1) You guys have a CPU scheduler? you mean user level thread Scheduler that maps user level threads to kernel level threads? I thought C++ by default creates native kernel threads but sure nothing will stop someone to create a user level scheduling library if that's what you are talking

Re: scylladb

Agreed, I'd recommend to treat benchmarks as a rough guide to see where there is potential, and follow through with your own tests. On 03/11/2017 09:37 PM, Edward Capriolo wrote: Benchmarks are great for FUDly blog posts. Real world work loads matter more. Every NoSQL vendor wins their

Re: scylladb

Sent: Thursday, March 9, 2017 14:21 To: user@cassandra.apache.org <mailto:user@cassandra.apache.org> Subject: Re: scylladb The comparison is fair, and conservative. Did substantial performance comparisons

Re: scylladb

claims instead of stating it. >>> >>> >>> On Thu, Mar 9, 2017 at 3:22 PM, Richard L. Burton III < >>> mrbur...@gmail.com> wrote: >>> >>>> They spend an enormous amount of time focusing on performance. You can >>>>

Re: scylladb

enormous amount of time focusing on performance. You can >>> expect them to continue on with their optimization and keep crushing it. >>> >>> P.S., I don't work for ScyllaDB. >>> >>> On Thu, Mar 9, 2017 at 6:02 PM, Rakesh Kumar <rakeshkumar...@outlook.com >>> > wrote: >>> >&g

Re: scylladb

till the difference looks staggering. From: daemeon reiydelle <daeme...@gmail.com <mailto:daeme...@gmail.com>> Sent: Thursday, March 9, 2017 14:21 To: user@cassandra.apache.org <mailto

Re: scylladb

t; jacques-henri.berthe...@genesys.com> wrote: >>> >>>> Cassandra is not about pure performance, there are many other DBs that >>>> are much faster than Cassandra. Cassandra strength is all about >>>> scalability, performance increases in a linear way as you add

Re: scylladb

10k node cluster. The >>> usual limiting factor is your disk write speed and latency, I don’t see how >>> C++ changes anything in this regard unless you can cache all your data in >>> memory. >>> >>> >>> >>> I’d be curious to know how ScyllaDB pe

Re: scylladb

ency, I don’t see how >> C++ changes anything in this regard unless you can cache all your data in >> memory. >> >> >> >> I’d be curious to know how ScyllaDB performs with a 100+ nodes cluster >> with PBs of data compared to Cassandra. >> >> *--* >

Re: scylladb

sh Kumar [mailto:rakeshkumar...@outlook.com] > *Sent:* vendredi 10 mars 2017 09:58 > > *To:* user@cassandra.apache.org > *Subject:* Re: scylladb > > > > Cassanda vs Scylla is a valid comparison because they both are > compatible. Scylla is a drop-in replaceme

RE: scylladb

: Rakesh Kumar [mailto:rakeshkumar...@outlook.com] Sent: vendredi 10 mars 2017 09:58 To: user@cassandra.apache.org Subject: Re: scylladb Cassanda vs Scylla is a valid comparison because they both are compatible. Scylla is a drop-in replacement for Cassandra. Is Aerospike a drop-in replacement

Re: scylladb

<bhu1ra...@gmail.com> To: user@cassandra.apache.org Sent: Friday, March 10, 2017 11:59 AM Subject: Re: scylladb Agreed C++ gives an added advantage to talk to underlying hardware with better efficiency, it sound good but can a pice of code written in C++ give 1000% throughput than a Ja

Re: scylladb

eshkumar...@outlook.com> >> wrote: >> >>> In all of their presentation they keep harping on the fact that scylladb >>> is written in C++ and does not carry the overhead of Java. Still the >>> difference looks staggering. >>>

Re: scylladb

elle <daeme...@gmail.com <mailto:daeme...@gmail.com>> Sent: Thursday, March 9, 2017 14:21 To: user@cassandra.apache.org <mailto:user@cassandra.apache.org> Subject: Re: scylladb The comparison is fair, and conservative. Did substantial performance

Re: scylladb

___ >>> From: daemeon reiydelle <daeme...@gmail.com> >>> Sent: Thursday, March 9, 2017 14:21 >>> To: user@cassandra.apache.org >>> Subject: Re: scylladb >>> >>> The comparison is fair, and conservative. Did substantial performance

Re: scylladb

Java. Still the >> difference looks staggering. >> >> From: daemeon reiydelle <daeme...@gmail.com> >> Sent: Thursday, March 9, 2017 14:21 >> To: user@cassandra.apache.org >> Subject: Re: scylladb >> >> The

Re: scylladb

gt; To: user@cassandra.apache.org > Subject: Re: scylladb > > The comparison is fair, and conservative. Did substantial performance > comparisons for two clients, both results returned throughputs that were > faster than the published comparisons (15x as I recall). At that time the &g

Re: scylladb

14:21 To: user@cassandra.apache.org Subject: Re: scylladb The comparison is fair, and conservative. Did substantial performance comparisons for two clients, both results returned throughputs that were faster than the published comparisons (15x as I recall). At that time the client preferred to u

Re: scylladb

I just did a Twitter search on scylladb and did not see any tweets about actual use, so far. -- Jack Krupansky On Wed, Nov 11, 2015 at 10:54 AM, Carlos Alonso wrote: > Any update about this? > > @Carlos Rolo, did you tried it? Thoughts? > > Carlos Alonso | Software

Re: scylladb

Killer, @cjrolo. Will you update via this thread? On Wed, Nov 11, 2015 at 7:57 AM, Carlos Rolo wrote: > Not yet, but not far from doing it. No rain here yet! :) > > On a more serious tone, should be done before end of the Month. > > -- > > > > -- [image: datastax_logo.png]

Re: scylladb

Sure! I have a lot of blog post on backlog to blog asap about this, otherwise I would only share results mid 2016 :P Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo

Re: scylladb

Not yet, but not far from doing it. No rain here yet! :) On a more serious tone, should be done before end of the Month. -- --

Re: scylladb

Any update about this? @Carlos Rolo, did you tried it? Thoughts? Carlos Alonso | Software Engineer | @calonso On 5 November 2015 at 14:07, Carlos Rolo wrote: > Something to do on a expected rainy weekend. Thanks for the information. > > Regards,

Re: scylladb

Nope, no one I know. Let me know if you try it I'd love to hear your feedback. > On Nov 5, 2015, at 9:22 AM, tommaso barbugli wrote: > > Hi guys, > > did anyone already try Scylladb (yet another fastest NoSQL database in town) > and has some thoughts/hands-on experience

Re: scylladb

I will not try until multi-DC is implemented. More than an month has passed since I looked for it, so it could possibly be in place, if so I may take some time to test it. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin:

Re: scylladb

As of two days ago, they say they've got it @cjrolo. https://github.com/scylladb/scylla/wiki/RELEASE-Scylla-0.11-Beta On Thursday, November 5, 2015, Carlos Rolo wrote: > I will not try until multi-DC is implemented. More than an month has > passed since I looked for it, so it

Re: scylladb

Something to do on a expected rainy weekend. Thanks for the information. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo * Mobile: +351 91 891 81

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

. It seems like a huge milestone achieved by Cassandra community, congratulations! From: user@cassandra.apache.org Subject: Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL Looking at the architecture and what scylladb does, I'm not surprised they got 10x improvement. SeaStar skips a lot

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

Looking at the architecture and what scylladb does, I'm not surprised they got 10x improvement. SeaStar skips a lot of the overhead of copying stuff and it gives them CPU core affinity. Anyone that's listened to Clif Click talk about cache misses, locks and other low level stuff would recognize

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

Tzach, Can you point to any documentation on scylladb site which talks about how/why scylla db performs better than Cassandra while using the same architecture? Regards Sachin On Tue, Sep 22, 2015 at 9:18 AM, Tzach Livyatan wrote: > Hello Cassandra users, > > We are

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

First glance at their github, it looks like they re-implemented Cassandra in C++. 90% components in Cassandra are in scylladb, i.e. compaction, repair, CQL, gossip, SStable. With C++, I believe this helps performance to some extent up to a point when compaction has not run yet. Then, it will be

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

I came across this article: zdnet.com/article/kvm-creators-open-source-fast-cassandra-drop-in-replacement-scylla/ Tzach, I would love to know/understand moree about ScyllaDB too. Also the benchmark seems to have only 1 DB Server. Do you have benchmark numbers where more than 1 DB servers were

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

On Wed, Sep 23, 2015 at 12:20 AM, Minh Do wrote: > First glance at their github, it looks like they re-implemented Cassandra > in C++. 90% components in Cassandra are > in scylladb, i.e. compaction, repair, CQL, gossip, SStable. > True > > > With C++, I believe this helps

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

On Wed, Sep 23, 2015 at 12:13 AM, Venkatesh Arivazhagan < venkey.a...@gmail.com> wrote: > I came across this article: > zdnet.com/article/kvm-creators-open-source-fast-cassandra-drop-in-replacement-scylla/ > > Tzach, I would love to know/understand moree about ScyllaDB too. Also the > benchmark

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

very interesting. I'm glad to see someone building a drop in replacement for Cassandra. On Tue, Sep 22, 2015 at 5:40 PM, Tzach Livyatan wrote: > Hi Sachin > > On Tue, Sep 22, 2015 at 11:40 PM, Sachin Nikam wrote: > >> Tzach, >> Can you point to

Re: ScyllaDB, a new open source, Cassandra-compatible NoSQL

Hi Sachin On Tue, Sep 22, 2015 at 11:40 PM, Sachin Nikam wrote: > Tzach, > Can you point to any documentation on scylladb site which talks about > how/why scylla db performs better than Cassandra while using the same > architecture? > see here