[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16645:
-
Fix Version/s: (was: 4.0.x)
4.0
4.0-rc2
Source Control Link:
https://github.com/apache/cassandra/commit/438a9c835abefac18dea8b6fbb422d75ac1b2b15
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thank you, committed.
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0-rc2, 4.0
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it I saw a performance degradation for Java 8.
> After a discussion among the community, it was decided to wait with _CRC32C_
> until Java 8 support is abandoned. The purpose of this ticket is to merge the
> benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> [https://github.com/apache/cassandra/pull/951/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16645:
-
Status: Ready to Commit (was: Review In Progress)
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it I saw a performance degradation for Java 8.
> After a discussion among the community, it was decided to wait with _CRC32C_
> until Java 8 support is abandoned. The purpose of this ticket is to merge the
> benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> [https://github.com/apache/cassandra/pull/951/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16645:
-
Reviewers: Brandon Williams
Status: Review In Progress (was: Patch Available)
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it I saw a performance degradation for Java 8.
> After a discussion among the community, it was decided to wait with _CRC32C_
> until Java 8 support is abandoned. The purpose of this ticket is to merge the
> benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> [https://github.com/apache/cassandra/pull/951/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Test and Documentation Plan: No tests or documentation are required.
Status: Patch Available (was: Open)
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it I saw a performance degradation for Java 8.
> After a discussion among the community, it was decided to wait with _CRC32C_
> until Java 8 support is abandoned. The purpose of this ticket is to merge the
> benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> [https://github.com/apache/cassandra/pull/951/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Description:
h2. Overview
As a part CASSANDRA-16360 there was a need to change the checksum algo from
_CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
it would be nice to have a way to measure performance for checksum calculation
(similarly to {{HashingBench}} for hash calculation).
In fact, the microbenchmark has been already created as a part of that ticket.
However, after running it I saw a performance degradation for Java 8. After a
discussion among the community, it was decided to wait with _CRC32C_ until Java
8 support is abandoned. The purpose of this ticket is to merge the benchmark
changes separately.
h2. What needs to be done
* Create a microbenchmark
h2. Link to PR
[https://github.com/apache/cassandra/pull/951/files]
was:
h2. Overview
As a part CASSANDRA-16360 there was a need to change the checksum algo from
_CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
it would be nice to have a way to measure performance for checksum calculation
(similarly to {{HashingBench}} for hash calculation).
In fact, the microbenchmark has been already created as a part of that ticket.
However, after running it we saw a performance degradation for Java 8 and
decided to wait until Java 8 support is abandoned. The purpose of this ticket
is to merge the benchmark changes separately.
h2. What needs to be done
* Create a microbenchmark
h2. Link to PR
https://github.com/apache/cassandra/pull/951/files
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it I saw a performance degradation for Java 8.
> After a discussion among the community, it was decided to wait with _CRC32C_
> until Java 8 support is abandoned. The purpose of this ticket is to merge the
> benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> [https://github.com/apache/cassandra/pull/951/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Description:
h2. Overview
As a part CASSANDRA-16360 there was a need to change the checksum algo from
_CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
it would be nice to have a way to measure performance for checksum calculation
(similarly to {{HashingBench}} for hash calculation).
In fact, the microbenchmark has been already created as a part of that ticket.
However, after running it we saw a performance degradation for Java 8 and
decided to wait until Java 8 support is abandoned. The purpose of this ticket
is to merge the benchmark changes separately.
h2. What needs to be done
* Create a microbenchmark
h2. Link to PR
https://github.com/apache/cassandra/pull/951/files
was:
h2. Overview
As a part CASSANDRA-16360 there was a need to change the checksum algo from
_CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
it would be nice to have a way to measure performance for checksum calculation
(similarly to {{HashingBench}} for hash calculation).
In fact, the microbenchmark has been already created as a part of that ticket.
However, after running it we saw a performance degradation for Java 8 and
decided to wait until Java 8 support is abandoned. The purpose of this ticket
is to merge the benchmark changes separately.
h2. What needs to be done
* Create a microbenchmark
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it we saw a performance degradation for Java 8
> and decided to wait until Java 8 support is abandoned. The purpose of this
> ticket is to merge the benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
> h2. Link to PR
> https://github.com/apache/cassandra/pull/951/files
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Priority: Low (was: Normal)
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it we saw a performance degradation for Java 8
> and decided to wait until Java 8 support is abandoned. The purpose of this
> ticket is to merge the benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Fix Version/s: 4.0.x
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it we saw a performance degradation for Java 8
> and decided to wait until Java 8 support is abandoned. The purpose of this
> ticket is to merge the benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16645) Add a microbenchmark for checksum calculation
[
https://issues.apache.org/jira/browse/CASSANDRA-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zotov updated CASSANDRA-16645:
-
Change Category: Performance
Complexity: Low Hanging Fruit
Status: Open (was: Triage Needed)
> Add a microbenchmark for checksum calculation
> -
>
> Key: CASSANDRA-16645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16645
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/benchmark
>Reporter: Alexey Zotov
>Assignee: Alexey Zotov
>Priority: Low
> Fix For: 4.0.x
>
>
> h2. Overview
> As a part CASSANDRA-16360 there was a need to change the checksum algo from
> _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change
> it would be nice to have a way to measure performance for checksum
> calculation (similarly to {{HashingBench}} for hash calculation).
> In fact, the microbenchmark has been already created as a part of that
> ticket. However, after running it we saw a performance degradation for Java 8
> and decided to wait until Java 8 support is abandoned. The purpose of this
> ticket is to merge the benchmark changes separately.
> h2. What needs to be done
> * Create a microbenchmark
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
