[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2018-11-14 Thread Ariel Weisberg (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ariel Weisberg updated CASSANDRA-11939:
---
Reviewers: Ariel Weisberg
 Reviewer: Ariel Weisberg

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
> Attachments: 11939-2.2.txt, 11939-2.2.txt, 11939-3.0.txt, 
> 11939-3.0.txt, 11939-3.11.txt, 11939-3.11.txt, 11939-output.txt, 
> 11939-trunk.txt, 11939-trunk.txt
>
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2018-11-14 Thread Amanda R Debrot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amanda R Debrot updated CASSANDRA-11939:

Attachment: 11939-2.2.txt
11939-3.0.txt
11939-3.11.txt
11939-trunk.txt
Status: Patch Available  (was: Open)

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
> Attachments: 11939-2.2.txt, 11939-2.2.txt, 11939-3.0.txt, 
> 11939-3.0.txt, 11939-3.11.txt, 11939-3.11.txt, 11939-output.txt, 
> 11939-trunk.txt, 11939-trunk.txt
>
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2018-11-14 Thread Amanda R Debrot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amanda R Debrot updated CASSANDRA-11939:

Attachment: 11939-trunk.txt

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
> Attachments: 11939-2.2.txt, 11939-3.0.txt, 11939-3.11.txt, 
> 11939-trunk.txt
>
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2018-11-14 Thread Amanda R Debrot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amanda R Debrot updated CASSANDRA-11939:

Attachment: 11939-output.txt

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
> Attachments: 11939-2.2.txt, 11939-3.0.txt, 11939-3.11.txt, 
> 11939-output.txt, 11939-trunk.txt
>
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2018-11-14 Thread Amanda R Debrot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amanda R Debrot updated CASSANDRA-11939:

Attachment: 11939-2.2.txt
11939-3.0.txt
11939-3.11.txt

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
> Attachments: 11939-2.2.txt, 11939-3.0.txt, 11939-3.11.txt
>
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2016-06-03 Thread Sylvain Lebresne (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylvain Lebresne updated CASSANDRA-11939:
-
Labels: lhf  (was: )

> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>  Labels: lhf
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read LatencyPartition Size
> Cell Count
>   (micros)  (micros)   (bytes)
> 50% 4.00 17.00770.00  8239
>  4
> 75% 5.00 24.00924.00 17084
> 17
> 95% 5.00 35.00  61214.00 51012
> 24
> 98% 6.00 35.00 126934.00105778
> 24
> 99% 6.00 72.00 152321.00152321
> 35
> Min 0.00  9.00 36.0021
>  0
> Max 6.00 86.00 263210.00  20924300
>   1109
> Percentile  Read Latency Write Latency Range Latency
> (micros)  (micros)  (micros)
> 50%  1331.00535.00  11864.00
> 75% 17084.00642.00  20501.00
> 95%219342.00   1331.00  20501.00
> 98%315852.00   2759.00  20501.00
> 99%379022.00   3311.00  20501.00
> Min   373.00 73.00   9888.00
> Max379022.00   9887.00  20501.00
> {code}
> Ideally read and write latencies should be in the same order and the first 
> and second columns on both so they’re directly aligned.  The sstables column 
> should be moved to the 3rd column to make way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2016-06-01 Thread J.B. Langston (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.B. Langston updated CASSANDRA-11939:
--
Description: 
It’s triggering my ocd that read and write latency columns are swapped in 
proxyhistograms vs cfhistograms. I guess the argument against changing it now 
is that it could screw with some peoples scripts or expectations, but it does 
make it hard to eyeball when you’re trying to compare local latencies vs 
coordinator latencies.

{code}
Percentile  SSTables Write Latency  Read LatencyPartition Size  
  Cell Count
  (micros)  (micros)   (bytes)
50% 4.00 17.00770.00  8239  
   4
75% 5.00 24.00924.00 17084  
  17
95% 5.00 35.00  61214.00 51012  
  24
98% 6.00 35.00 126934.00105778  
  24
99% 6.00 72.00 152321.00152321  
  35
Min 0.00  9.00 36.0021  
   0
Max 6.00 86.00 263210.00  20924300  
1109

Percentile  Read Latency Write Latency Range Latency
(micros)  (micros)  (micros)
50%  1331.00535.00  11864.00
75% 17084.00642.00  20501.00
95%219342.00   1331.00  20501.00
98%315852.00   2759.00  20501.00
99%379022.00   3311.00  20501.00
Min   373.00 73.00   9888.00
Max379022.00   9887.00  20501.00
{code}

Ideally read and write latencies should be in the same order and the first and 
second columns on both so they’re directly aligned.  The sstables column should 
be moved to the 3rd column to make way.

  was:
It’s triggering my ocd that read and write latency columns are swapped in 
proxyhistograms vs cfhistograms. I guess the argument against changing it now 
is that it could screw with some peoples scripts or expectations, but it does 
make it hard to eyeball when you’re trying to compare local latencies vs 
coordinator latencies.

{code}
Percentile  SSTables Write Latency  Read LatencyPartition Size  
  Cell Count
  (micros)  (micros)   (bytes)
50% 4.00 17.00770.00  8239  
   4
75% 5.00 24.00924.00 17084  
  17
95% 5.00 35.00  61214.00 51012  
  24
98% 6.00 35.00 126934.00105778  
  24
99% 6.00 72.00 152321.00152321  
  35
Min 0.00  9.00 36.0021  
   0
Max 6.00 86.00 263210.00  20924300  
1109

Percentile  Read Latency Write Latency Range Latency
(micros)  (micros)  (micros)
50%  1331.00535.00  11864.00
75% 17084.00642.00  20501.00
95%219342.00   1331.00  20501.00
98%315852.00   2759.00  20501.00
99%379022.00   3311.00  20501.00
Min   373.00 73.00   9888.00
Max379022.00   9887.00  20501.00
{code}

Ideally read and write latencies should be in the same order and the first and 
second columns on both so they’re directly comparable.  The sstables column 
should be moved to the 3rd column to make way.


> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency  Read

[jira] [Updated] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

2016-06-01 Thread J.B. Langston (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.B. Langston updated CASSANDRA-11939:
--
Description: 
It’s triggering my ocd that read and write latency columns are swapped in 
proxyhistograms vs cfhistograms. I guess the argument against changing it now 
is that it could screw with some peoples scripts or expectations, but it does 
make it hard to eyeball when you’re trying to compare local latencies vs 
coordinator latencies.

{code}
Percentile  SSTables Write Latency  Read LatencyPartition Size  
  Cell Count
  (micros)  (micros)   (bytes)
50% 4.00 17.00770.00  8239  
   4
75% 5.00 24.00924.00 17084  
  17
95% 5.00 35.00  61214.00 51012  
  24
98% 6.00 35.00 126934.00105778  
  24
99% 6.00 72.00 152321.00152321  
  35
Min 0.00  9.00 36.0021  
   0
Max 6.00 86.00 263210.00  20924300  
1109

Percentile  Read Latency Write Latency Range Latency
(micros)  (micros)  (micros)
50%  1331.00535.00  11864.00
75% 17084.00642.00  20501.00
95%219342.00   1331.00  20501.00
98%315852.00   2759.00  20501.00
99%379022.00   3311.00  20501.00
Min   373.00 73.00   9888.00
Max379022.00   9887.00  20501.00
{code}

Ideally read and write latencies should be in the same order and the first and 
second columns on both so they’re directly comparable.  The sstables column 
should be moved to the 3rd column to make way.

  was:
It’s triggering my ocd that read and write latency columns are swapped in 
proxyhistograms vs cfhistograms. I guesst the argument against changing it now 
is that it could screw with some peoples scripts or expectations, but it does 
make it hard to eyeball when you’re trying to compare local latencies vs 
coordinator latencies.

{code}
Percentile  SSTables Write Latency  Read LatencyPartition Size  
  Cell Count
  (micros)  (micros)   (bytes)
50% 4.00 17.00770.00  8239  
   4
75% 5.00 24.00924.00 17084  
  17
95% 5.00 35.00  61214.00 51012  
  24
98% 6.00 35.00 126934.00105778  
  24
99% 6.00 72.00 152321.00152321  
  35
Min 0.00  9.00 36.0021  
   0
Max 6.00 86.00 263210.00  20924300  
1109

Percentile  Read Latency Write Latency Range Latency
(micros)  (micros)  (micros)
50%  1331.00535.00  11864.00
75% 17084.00642.00  20501.00
95%219342.00   1331.00  20501.00
98%315852.00   2759.00  20501.00
99%379022.00   3311.00  20501.00
Min   373.00 73.00   9888.00
Max379022.00   9887.00  20501.00
{code}

Ideally read and write latencies should be in the same order and the first and 
second columns on both so they’re directly comparable.  The sstables column 
should be moved to the 3rd column to make way.


> Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms
> -
>
> Key: CASSANDRA-11939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11939
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: J.B. Langston
>Priority: Minor
>
> It’s triggering my ocd that read and write latency columns are swapped in 
> proxyhistograms vs cfhistograms. I guess the argument against changing it now 
> is that it could screw with some peoples scripts or expectations, but it does 
> make it hard to eyeball when you’re trying to compare local latencies vs 
> coordinator latencies.
> {code}
> Percentile  SSTables Write Latency