cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14160) maxPurgeableTimestamp should traverse tables in order of minTimestamp
Date Tue, 17 Apr 2018 14:00:00 GMT


Marcus Eriksson commented on CASSANDRA-14160:

hey [~josnyder] the code looks good to me, but, as [~jjirsa] mentioned above, a unit test
that makes sure the sstables are returned in the correct order should be added. You also mentioned
a that you had not yet benchmarked the change, have you done that? If not, that would also
be nice.

> maxPurgeableTimestamp should traverse tables in order of minTimestamp
> ---------------------------------------------------------------------
>                 Key: CASSANDRA-14160
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Josh Snyder
>            Assignee: Josh Snyder
>            Priority: Major
>              Labels: performance
>             Fix For: 4.x
> 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|]
to demonstrate this possibility.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message