[jira] [Comment Edited] (CASSANDRA-4545) add cql support for batchlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461812#comment-13461812 ] Aleksey Yeschenko edited comment on CASSANDRA-4545 at 9/25/12 1:07 AM: --- No option looks ideal atm, so here is another non-ideal one: leave current syntax as is and add BEGIN FULLY-ATOMIC BATCH (or COMPLETELY ATOMIC) for abm, not just ATOMIC, since regular batches have per-row atomicity. was (Author: iamaleksey): No options looks ideal atm, so here is another non-ideal one: leave current syntax as is and add BEGIN FULLY-ATOMIC BATCH (or COMPLETELY ATOMIC) for abm, not just ATOMIC, since regular batches have per-row atomicity. add cql support for batchlog Key: CASSANDRA-4545 URL: https://issues.apache.org/jira/browse/CASSANDRA-4545 Project: Cassandra Issue Type: Sub-task Reporter: Jonathan Ellis Assignee: Aleksey Yeschenko Need to expose the equivalent of atomic_batch_mutate (CASSANDRA-4542) to CQL3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CASSANDRA-4545) add cql support for batchlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461582#comment-13461582 ] Aleksey Yeschenko edited comment on CASSANDRA-4545 at 9/24/12 3:01 PM: --- Used a three-node cluster, rah modified cassandra-stress from a separate machine. cassandra-stress was modified to take keys-per-batch parameter. I wiped all the data, ran stress for regular batch mutate (three times for each kpb value, picking the average one), then wiped all the data again and ran the same benchmarks for atomic batch mutate. total in the output is total batches, not total keys (unlike in unmodified cassandra-stress). Default total number of keys was written every time (1M) with 5 columns per key and CL.ONE. # 1 key per batch ## batch_mutate 264131,26413,26413,0.001746815027391711,10 612819,34868,34868,0.0013791584453723674,20 988733,37591,37591,0.001265645865809733,30 100,1126,1126,9.46924647199787E-4,30 ## atomic_batch_mutate 116329,11632,11632,0.0039553851576133205,10 218728,10239,10239,0.0049213175909921,20 341348,12262,12262,0.004092179089871147,30 453569,11222,11222,0.00446199909107921,40 553009,9944,9944,0.005039782783588093,50 657635,10462,10462,0.004790099975149581,60 771908,11427,11427,0.004257716170924015,70 872911,10100,10100,0.005103590982446066,80 970814,9790,9790,0.003992002287978918,90 100,2918,2918,0.00181138216958,93 # 10 keys per batch ## batch_mutate 41456,4145,4145,0.009599430721729063,10 95977,5452,5452,0.00859437647878799,20 10,402,402,0.005297787720606513,21 ## atomic_batch_mutate 31813,3181,3181,0.01379417219375727,10 61825,3001,3001,0.017426962548314006,20 92392,3056,3056,0.013992279255406156,30 10,760,760,0.018285094637223973,34 # 100 keys per batch ## batch_mutate 5414,541,541,0.07286830439601034,10 1,458,458,0.06448626253815962,16 ## atomic_batch_mutate 4560,456,456,0.077079167,10 9037,447,447,0.10926133571588117,20 1,96,96,0.04469574247144341,22 # 1000 keys per batch ## batch_mutate 537,53,53,0.6769962756052141,10 1000,46,46,0.5918012958963282,16 ## atomic_batch_mutate 509,50,50,0.6374538310412574,10 1000,49,49,0.9193156822810591,20 # 1 keys per batch ## batch_mutate 40,4,4,7.91995,19 100,6,6,8.1601832,30 ## atomic_batch_mutate 17,1,1,6.496764705882353,19 36,1,1,11.307736842105264,29 98,6,6,15.237580645161291,40 100,0,0,2.745,40 I don't have an opinion yet regarding making abm the default batch mode, but these are some numbers. Please let me know if you need more (and what kinds of scenarios). was (Author: iamaleksey): Used a three-node cluster, rah modified cassandra-stress from a separate machine. cassandra-stress was modified to take keys-per-batch parameter. I wiped all the data, ran stress for regular batch mutate (three times for each kpb value, picking the average one), then wiped all the data again and ran the same benchmarks for atomic batch mutate. total in the output is total batches, not total keys (unlike in unmodified cassandra-stress). Default total number of keys was written every time (1M) with 5 columns per key and CL.ONE. # 1 key per batch ## batch_mutate 264131,26413,26413,0.001746815027391711,10 612819,34868,34868,0.0013791584453723674,20 988733,37591,37591,0.001265645865809733,30 100,1126,1126,9.46924647199787E-4,30 ## atomic_batch_mutate 116329,11632,11632,0.0039553851576133205,10 218728,10239,10239,0.0049213175909921,20 341348,12262,12262,0.004092179089871147,30 453569,11222,11222,0.00446199909107921,40 553009,9944,9944,0.005039782783588093,50 657635,10462,10462,0.004790099975149581,60 771908,11427,11427,0.004257716170924015,70 872911,10100,10100,0.005103590982446066,80 970814,9790,9790,0.003992002287978918,90 100,2918,2918,0.00181138216958,93 # 10 keys per batch ## batch_mutate 41456,4145,4145,0.009599430721729063,10 95977,5452,5452,0.00859437647878799,20 10,402,402,0.005297787720606513,21 ## atomic_batch_mutate 31813,3181,3181,0.01379417219375727,10 61825,3001,3001,0.017426962548314006,20 92392,3056,3056,0.013992279255406156,30 10,760,760,0.018285094637223973,34 # 100 keys per batch ## batch_mutate 5414,541,541,0.07286830439601034,10 1,458,458,0.06448626253815962,16 ## atomic_batch_mutate 4560,456,456,0.077079167,10 9037,447,447,0.10926133571588117,20 1,96,96,0.04469574247144341,22 # 1000 keys per batch ## batch_mutate 537,53,53,0.6769962756052141,10 1000,46,46,0.5918012958963282,16 ## atomic_batch_mutate 509,50,50,0.6374538310412574,10 1000,49,49,0.9193156822810591,20 # 1 keys per batch ## batch_mutate 40,4,4,7.91995,19 100,6,6,8.1601832,30 ## atomic_batch_mutate 17,1,1,6.496764705882353,19 36,1,1,11.307736842105264,29 98,6,6,15.237580645161291,40 100,0,0,2.745,40 I don't have an opinion yet regarding making abm the default batch mode, but these are some numbers. Please let
[jira] [Comment Edited] (CASSANDRA-4545) add cql support for batchlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461582#comment-13461582 ] Aleksey Yeschenko edited comment on CASSANDRA-4545 at 9/24/12 3:02 PM: --- Used a three-node cluster, ran modified cassandra-stress from a separate machine. cassandra-stress was modified to take keys-per-batch parameter. I wiped all the data, ran stress for regular batch mutate (three times for each kpb value, picking the average one), then wiped all the data again and ran the same benchmarks for atomic batch mutate. total in the output is total batches, not total keys (unlike in unmodified cassandra-stress). Default total number of keys was written every time (1M) with 5 columns per key and CL.ONE. # 1 key per batch ## batch_mutate 264131,26413,26413,0.001746815027391711,10 612819,34868,34868,0.0013791584453723674,20 988733,37591,37591,0.001265645865809733,30 100,1126,1126,9.46924647199787E-4,30 ## atomic_batch_mutate 116329,11632,11632,0.0039553851576133205,10 218728,10239,10239,0.0049213175909921,20 341348,12262,12262,0.004092179089871147,30 453569,11222,11222,0.00446199909107921,40 553009,9944,9944,0.005039782783588093,50 657635,10462,10462,0.004790099975149581,60 771908,11427,11427,0.004257716170924015,70 872911,10100,10100,0.005103590982446066,80 970814,9790,9790,0.003992002287978918,90 100,2918,2918,0.00181138216958,93 # 10 keys per batch ## batch_mutate 41456,4145,4145,0.009599430721729063,10 95977,5452,5452,0.00859437647878799,20 10,402,402,0.005297787720606513,21 ## atomic_batch_mutate 31813,3181,3181,0.01379417219375727,10 61825,3001,3001,0.017426962548314006,20 92392,3056,3056,0.013992279255406156,30 10,760,760,0.018285094637223973,34 # 100 keys per batch ## batch_mutate 5414,541,541,0.07286830439601034,10 1,458,458,0.06448626253815962,16 ## atomic_batch_mutate 4560,456,456,0.077079167,10 9037,447,447,0.10926133571588117,20 1,96,96,0.04469574247144341,22 # 1000 keys per batch ## batch_mutate 537,53,53,0.6769962756052141,10 1000,46,46,0.5918012958963282,16 ## atomic_batch_mutate 509,50,50,0.6374538310412574,10 1000,49,49,0.9193156822810591,20 # 1 keys per batch ## batch_mutate 40,4,4,7.91995,19 100,6,6,8.1601832,30 ## atomic_batch_mutate 17,1,1,6.496764705882353,19 36,1,1,11.307736842105264,29 98,6,6,15.237580645161291,40 100,0,0,2.745,40 I don't have an opinion yet regarding making abm the default batch mode, but these are some numbers. Please let me know if you need more (and what kinds of scenarios). was (Author: iamaleksey): Used a three-node cluster, rah modified cassandra-stress from a separate machine. cassandra-stress was modified to take keys-per-batch parameter. I wiped all the data, ran stress for regular batch mutate (three times for each kpb value, picking the average one), then wiped all the data again and ran the same benchmarks for atomic batch mutate. total in the output is total batches, not total keys (unlike in unmodified cassandra-stress). Default total number of keys was written every time (1M) with 5 columns per key and CL.ONE. # 1 key per batch ## batch_mutate 264131,26413,26413,0.001746815027391711,10 612819,34868,34868,0.0013791584453723674,20 988733,37591,37591,0.001265645865809733,30 100,1126,1126,9.46924647199787E-4,30 ## atomic_batch_mutate 116329,11632,11632,0.0039553851576133205,10 218728,10239,10239,0.0049213175909921,20 341348,12262,12262,0.004092179089871147,30 453569,11222,11222,0.00446199909107921,40 553009,9944,9944,0.005039782783588093,50 657635,10462,10462,0.004790099975149581,60 771908,11427,11427,0.004257716170924015,70 872911,10100,10100,0.005103590982446066,80 970814,9790,9790,0.003992002287978918,90 100,2918,2918,0.00181138216958,93 # 10 keys per batch ## batch_mutate 41456,4145,4145,0.009599430721729063,10 95977,5452,5452,0.00859437647878799,20 10,402,402,0.005297787720606513,21 ## atomic_batch_mutate 31813,3181,3181,0.01379417219375727,10 61825,3001,3001,0.017426962548314006,20 92392,3056,3056,0.013992279255406156,30 10,760,760,0.018285094637223973,34 # 100 keys per batch ## batch_mutate 5414,541,541,0.07286830439601034,10 1,458,458,0.06448626253815962,16 ## atomic_batch_mutate 4560,456,456,0.077079167,10 9037,447,447,0.10926133571588117,20 1,96,96,0.04469574247144341,22 # 1000 keys per batch ## batch_mutate 537,53,53,0.6769962756052141,10 1000,46,46,0.5918012958963282,16 ## atomic_batch_mutate 509,50,50,0.6374538310412574,10 1000,49,49,0.9193156822810591,20 # 1 keys per batch ## batch_mutate 40,4,4,7.91995,19 100,6,6,8.1601832,30 ## atomic_batch_mutate 17,1,1,6.496764705882353,19 36,1,1,11.307736842105264,29 98,6,6,15.237580645161291,40 100,0,0,2.745,40 I don't have an opinion yet regarding making abm the default batch mode, but these are some numbers. Please let
