[
https://issues.apache.org/jira/browse/CASSANDRA-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312266#comment-14312266
]
J.B. Langston commented on CASSANDRA-8730:
------------------------------------------
[~iamaleksey] This is the schema I am testing against. It uses uuid and
timestamp (not timeuuid):
{code}
CREATE TABLE x (
a bigint,
b bigint,
c timestamp,
d uuid,
e text,
f text,
g text,
h float,
PRIMARY KEY ((a, b), c, d)
) WITH CLUSTERING ORDER BY (ts DESC, uuid DESC) AND
bloom_filter_fp_chance=0.010000 AND
caching='KEYS_ONLY' AND
comment='' AND
dclocal_read_repair_chance=0.100000 AND
gc_grace_seconds=0 AND
index_interval=128 AND
read_repair_chance=0.000000 AND
replicate_on_write='true' AND
populate_io_cache_on_flush='false' AND
default_time_to_live=0 AND
speculative_retry='99.0PERCENTILE' AND
memtable_flush_period_in_ms=0 AND
compaction={'class': 'SizeTieredCompactionStrategy'} AND
compression={'sstable_compression': 'LZ4Compressor'};
{code}
> 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: 2.1.4
>
>
> 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)
