[
https://issues.apache.org/jira/browse/CASSANDRA-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347767#comment-14347767
]
Ariel Weisberg commented on CASSANDRA-8730:
-------------------------------------------
I've gone over this a couple of times. It looks okay and the tests are
persuasive that they check that the comparisons are self-consistent. Maybe
resurrect the old versions to check that they are prior version consistent in
the unit tests. Maybe modify the test to use a seeded RNG with a known seed and
print it out so if there is a failure we can reproduce.
UUIDType is supposed to correctly compare TimeUUIDTypes and there is some cut
and paste so it maybe it should use TimeUUID in parallel and see if both
approaches return the same answer when LHS and RHS are both Time UUIDs?
What is UUIDTypeTest.permute used to check for?
> Optimize UUIDType comparisons
> -----------------------------
>
> Key: CASSANDRA-8730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8730
> Project: Cassandra
> Issue Type: Improvement
> Reporter: J.B. Langston
> Assignee: Benedict
> Fix For: 3.0
>
>
> Compaction is slow on tables using compound keys containing UUIDs due to
> being CPU bound by key comparison. [~benedict] said he sees some easy
> optimizations that could be made for UUID comparison.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
