You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Josh Snyder (JIRA)" <ji...@apache.org> on 2018/01/10 18:17:00 UTC

[jira] [Created] (CASSANDRA-14160) maxPurgeableTimestamp should traverse tables in order of minTimestamp

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