Re: Performance Tickets
I'd put https://issues.apache.org/jira/browse/CASSANDRA-6060 and https://issues.apache.org/jira/browse/CASSANDRA-4175 on the high priority list too. Do less work can be even more effective than do the same work faster. On Tue, Apr 15, 2014 at 8:28 AM, Benedict Elliott Smith belliottsm...@datastax.com wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance Tickets
- CASSANDRA-5220: Repair improvements when using vnodes That definitely deserves a performance tag. Yuki, are you looking at this or should we unassign in case somebody else wants to jump in? On 15 April 2014 14:59, Michael Shuler mich...@pbandjelly.org wrote: On 04/15/2014 08:28 AM, Benedict Elliott Smith wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? - CASSANDRA-5220: Repair improvements when using vnodes Not sure where that might go in your difficulty ordering, but since vnodes are default and repair time seems to be a pretty common question/pain, it's important for ops and highly relevant to cluster performance. If some of the above list might directly affect/help repair performance, let's get them tied together in Jira :) -- Kind regards, Michael
Re: Performance Tickets
Yes, I have an idea forming up in my mind for 5220, so I'm still on it. On Wed, Apr 16, 2014 at 6:25 AM, Benedict Elliott Smith belliottsm...@datastax.com wrote: - CASSANDRA-5220: Repair improvements when using vnodes That definitely deserves a performance tag. Yuki, are you looking at this or should we unassign in case somebody else wants to jump in? On 15 April 2014 14:59, Michael Shuler mich...@pbandjelly.org wrote: On 04/15/2014 08:28 AM, Benedict Elliott Smith wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? - CASSANDRA-5220: Repair improvements when using vnodes Not sure where that might go in your difficulty ordering, but since vnodes are default and repair time seems to be a pretty common question/pain, it's important for ops and highly relevant to cluster performance. If some of the above list might directly affect/help repair performance, let's get them tied together in Jira :) -- Kind regards, Michael -- Yuki Morishita t:yukim (http://twitter.com/yukim)
Performance Tickets
It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed?
Re: Performance Tickets
On 04/15/2014 08:28 AM, Benedict Elliott Smith wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? - CASSANDRA-5220: Repair improvements when using vnodes Not sure where that might go in your difficulty ordering, but since vnodes are default and repair time seems to be a pretty common question/pain, it's important for ops and highly relevant to cluster performance. If some of the above list might directly affect/help repair performance, let's get them tied together in Jira :) -- Kind regards, Michael
Re: Performance Tickets
And here's the Grand List of all performance tickets: https://issues.apache.org/jira/issues/?jql=labels%20%3D%20performance%20and%20project%20%3D%20CASSANDRA%20AND%20status!%3Dresolved Benedict, you might want to un-assign from yourself anything you're not working on in the near future in case anyone else wants to grab one. On Tue, Apr 15, 2014 at 3:28 PM, Benedict Elliott Smith belliottsm...@datastax.com wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance Tickets
I thought I'd spammed the change list enough for one day, but since you mention it... :-) On 15 April 2014 23:40, Jonathan Ellis jbel...@gmail.com wrote: And here's the Grand List of all performance tickets: https://issues.apache.org/jira/issues/?jql=labels%20%3D%20performance%20and%20project%20%3D%20CASSANDRA%20AND%20status!%3Dresolved Benedict, you might want to un-assign from yourself anything you're not working on in the near future in case anyone else wants to grab one. On Tue, Apr 15, 2014 at 3:28 PM, Benedict Elliott Smith belliottsm...@datastax.com wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on. - CASSANDRA-7039: DirectByteBuffer compatible LZ4 methods - CASSANDRA-6726: RAR/CRAR off-heap - CASSANDRA-6633: Dynamic bloom filter resizing - CASSANDRA-6755: Optimise CellName/Composite comparisons for NativeCell - CASSANDRA-7032: Improve vnode allocation - CASSANDRA-6809: Compressed Commit Log - CASSANDRA-5663: write batching in native protocol - CASSANDRA-5863: In-process (uncompressed) page cache - CASSANDRA-7040: Replace read/write stage with per-disk access coordination - CASSANDRA-6917: enum data type - CASSANDRA-6935: Make clustering part of primary key a first order component in the storage engine I've arranged them in ascending order of my intuitive impression of their difficulty. Don't all leap at the last few :) Anything I've missed? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
I've tagged the issues in this thread with the Performance label for easier tracking: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012310865%20AND%20labels%20%3D%20performance%20and%20status%3Dopen On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
(should be): I'm happy to work on it On Fri, Sep 20, 2013 at 1:34 PM, Jason Brown jasedbr...@gmail.com wrote: Ha. I've actually been hacking that today. I'm glad to it on On Sep 20, 2013 1:15 PM, Jonathan Ellis jbel...@gmail.com wrote: https://issues.apache.org/jira/browse/CASSANDRA-1632 (Thread workflow and cpu affinity) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Ha. I've actually been hacking that today. I'm glad to it on On Sep 20, 2013 1:15 PM, Jonathan Ellis jbel...@gmail.com wrote: https://issues.apache.org/jira/browse/CASSANDRA-1632 (Thread workflow and cpu affinity) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
https://issues.apache.org/jira/browse/CASSANDRA-3578 (Mulithreaded commitlog) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Performance tickets
I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
https://issues.apache.org/jira/browse/CASSANDRA-5357 (query cache) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Hi Jonathan, I can take on first two (4817, 5863). Best Regards, Pavel. On Sep 19, 2013, at 8:46 AM, Jonathan Ellis jbel...@gmail.com wrote: https://issues.apache.org/jira/browse/CASSANDRA-5357 (query cache) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Fantastic! On Thu, Sep 19, 2013 at 10:57 AM, Pavel Yaskevich pove...@gmail.com wrote: Hi Jonathan, I can take on first two (4817, 5863). Best Regards, Pavel. On Sep 19, 2013, at 8:46 AM, Jonathan Ellis jbel...@gmail.com wrote: https://issues.apache.org/jira/browse/CASSANDRA-5357 (query cache) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Also https://issues.apache.org/jira/browse/CASSANDRA-4338 (retaining both this and https://issues.apache.org/jira/browse/CASSANDRA-5019) -- AY On Thursday, September 19, 2013 at 19:07 PM, Jonathan Ellis wrote: https://issues.apache.org/jira/browse/CASSANDRA-5549 (remove Table.switchlock) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
I can take on 4175 and maybe 5019 or 6060. Please assign at will :) On Sep 19, 2013 9:02 AM, Jonathan Ellis jbel...@gmail.com wrote: Fantastic! On Thu, Sep 19, 2013 at 10:57 AM, Pavel Yaskevich pove...@gmail.com wrote: Hi Jonathan, I can take on first two (4817, 5863). Best Regards, Pavel. On Sep 19, 2013, at 8:46 AM, Jonathan Ellis jbel...@gmail.com wrote: https://issues.apache.org/jira/browse/CASSANDRA-5357 (query cache) On Thu, Sep 19, 2013 at 10:43 AM, Jonathan Ellis jbel...@gmail.com wrote: I'd like to spend some effort in 2.1 improving our performance story for non-io-bound workloads. Here are some of the ideas we have floating around: https://issues.apache.org/jira/browse/CASSANDRA-4718 (context switch overhead) https://issues.apache.org/jira/browse/CASSANDRA-5863 (decompressed chunk cache) https://issues.apache.org/jira/browse/CASSANDRA-5417 (composites optimization) https://issues.apache.org/jira/browse/CASSANDRA-5019 (flyweight cell container) https://issues.apache.org/jira/browse/CASSANDRA-5020 (switch off of ByteBuffers in cell names and values. Jake was also looking at using primitives instead; I don't think there's a ticket for that?) https://issues.apache.org/jira/browse/CASSANDRA-4175 (cell name compression) https://issues.apache.org/jira/browse/CASSANDRA-6060 (avoid using Strings internally for ks/cf identifiers) Anything else I'm missing? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Seeing Sylvain's comment to hold off on 4175, do you mind if I take a whack at 6060? On Sep 19, 2013 9:35 AM, Jonathan Ellis jbel...@gmail.com wrote: Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
It's all yours. On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown jasedbr...@gmail.com wrote: Seeing Sylvain's comment to hold off on 4175, do you mind if I take a whack at 6060? On Sep 19, 2013 9:35 AM, Jonathan Ellis jbel...@gmail.com wrote: Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Well 5417 and 5020 combined On Thu, Sep 19, 2013 at 1:50 PM, Jake Luciani jak...@gmail.com wrote: I've been working on 5417 On Thu, Sep 19, 2013 at 1:33 PM, Jonathan Ellis jbel...@gmail.com wrote: It's all yours. On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown jasedbr...@gmail.com wrote: Seeing Sylvain's comment to hold off on 4175, do you mind if I take a whack at 6060? On Sep 19, 2013 9:35 AM, Jonathan Ellis jbel...@gmail.com wrote: Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- http://twitter.com/tjake -- http://twitter.com/tjake
Re: Performance tickets
I've been working on 5417 On Thu, Sep 19, 2013 at 1:33 PM, Jonathan Ellis jbel...@gmail.com wrote: It's all yours. On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown jasedbr...@gmail.com wrote: Seeing Sylvain's comment to hold off on 4175, do you mind if I take a whack at 6060? On Sep 19, 2013 9:35 AM, Jonathan Ellis jbel...@gmail.com wrote: Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- http://twitter.com/tjake
Re: Performance tickets
https://issues.apache.org/jira/browse/CASSANDRA-5549 (remove Table.switchlock) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Performance tickets
Hi Jonathan, I can try 5549, if you want. Regards, /VJ On Thu, Sep 19, 2013 at 10:50 AM, Jake Luciani jak...@gmail.com wrote: Well 5417 and 5020 combined On Thu, Sep 19, 2013 at 1:50 PM, Jake Luciani jak...@gmail.com wrote: I've been working on 5417 On Thu, Sep 19, 2013 at 1:33 PM, Jonathan Ellis jbel...@gmail.com wrote: It's all yours. On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown jasedbr...@gmail.com wrote: Seeing Sylvain's comment to hold off on 4175, do you mind if I take a whack at 6060? On Sep 19, 2013 9:35 AM, Jonathan Ellis jbel...@gmail.com wrote: Oh, I misunderstood him. 4175 is yours then! On Thu, Sep 19, 2013 at 11:19 AM, Jason Brown jasedbr...@gmail.com wrote: As Aleksey just claimed 5019 :), either of the other tickets is fine. On Sep 19, 2013 9:17 AM, Jonathan Ellis jbel...@gmail.com wrote: Those are maybe the 3 biggest ones here, how about 5019 to start with? :) On Thu, Sep 19, 2013 at 11:09 AM, Jason Brown jasedbr...@gmail.com wrote: I can take on 4175 and maybe 5019 or 6060. Please assign at will :) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- http://twitter.com/tjake -- http://twitter.com/tjake
