[ 
https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17619706#comment-17619706
 ] 

Andres de la Peña commented on CASSANDRA-17240:
-----------------------------------------------

{quote}The flakes in the memtable size test are now fixed. [~adelapena], you 
can rerun the above if you wish; I have already run both flaky ones, 
{{MemtableSizeOffheapObjectsTest}} and {{{}MemtableSizeOffheapBuffersTest{}}}, 
thousands of times.
{quote}
CASSANDRA-17939 has just been merged. It will create conflicts with the new job 
for tries that this patch adds. The changes on CircleCI config should be 
adapted to also add an associated job for repeatedly run any new, modified or 
manually specify unit tests with memtable tries. [The previously mentioned 
commit|https://github.com/adelapena/cassandra/commit/23fe8743f185ad1b93cce37383d6d4807ea14e36]
 does exactly that. It was meant to help with the rebase pains.

> CEP-19: Trie memtable implementation
> ------------------------------------
>
>                 Key: CASSANDRA-17240
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17240
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Memtable
>            Reporter: Branimir Lambov
>            Assignee: Branimir Lambov
>            Priority: Normal
>         Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, 
> density_SG.html.gz, density_test_with_sharding.html.gz, latency-1_1-95.png, 
> latency-9_1-95.png, throughput_SG.png, throughput_apache.png
>
>          Time Spent: 13h 20m
>  Remaining Estimate: 0h
>
> Trie-based memtable implementation as described in CEP-19, built on top of 
> CASSANDRA-17034 and CASSANDRA-6936.
> The implementation is available in this 
> [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to