cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Snyder (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-14160) maxPurgeableTimestamp should traverse tables in order of minTimestamp
Date Wed, 10 Jan 2018 18:17:00 GMT
Josh Snyder created CASSANDRA-14160:
---------------------------------------

             Summary: maxPurgeableTimestamp should traverse tables in order of minTimestamp
                 Key: CASSANDRA-14160
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14160
             Project: Cassandra
          Issue Type: Bug
          Components: Compaction
            Reporter: Josh Snyder


In maxPurgeableTimestamp, we iterate over the bloom filters of each overlapping SSTable. Of
the bloom filter hits, we take the SSTable with the lowest minTimestamp. If we kept the SSTables
in sorted order of minTimestamp, then we could short-circuit the operation at the first bloom
filter hit, reducing cache pressure (or worse, I/O) and CPU time.

I've written (but not yet benchmarked) [some code|https://github.com/hashbrowncipher/cassandra/commit/29859a4a2e617f6775be49448858bc59fdafab44]
to demonstrate this possibility.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message