[ 
https://issues.apache.org/jira/browse/CASSANDRA-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek Lewandowski updated CASSANDRA-18441:
------------------------------------------
    Test and Documentation Plan: regression tests
                         Status: Patch Available  (was: In Progress)

https://github.com/apache/cassandra/pull/2295
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/679/workflows/cb9987e4-cb8d-449b-aef8-1ea7829c19ea

Something which I've done additionally was more refactoring of autosaving cache 
- instead of just moving format ids to metadata, I moved all dictionaries to 
the metadata. It made the cache smaller and loading faster, especially for 
tables with no clustering keys.

Here are the results from some benchmark saving 2M rows in across 2 tables and 
200 sstables. 

|| UUID  || saving-trunk || saving-18441 || size-trunk || size-18441 || 
loading-trunk || loading-18441 ||
| true  | 952 ms       | 800 ms       |      72 MB |      30 MB |       5737 ms 
|        860 ms |
| false | 852 ms       | 822 ms       |     106 MB |      30 MB |       1058 ms 
|        800 ms |

SSTableFormat.Type is marked as deprecated as there is pretty little sense for 
it to exist. 


> Improvements to SSTable format configuration
> --------------------------------------------
>
>                 Key: CASSANDRA-18441
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18441
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/SSTable
>            Reporter: Branimir Lambov
>            Assignee: Jacek Lewandowski
>            Priority: Normal
>             Fix For: 5.x
>
>
> CEP-17 and CASSANDRA-17056 abstracted some interfaces for SSTable format 
> implementations and defined a method of plugging in specific configurations. 
> This method is brittle and asks users to specify format identifiers whose 
> configuration does not provide value but can be the source of conflicts and 
> problems. On the other hand it makes important choices non-obvious, as the 
> selection of format to write is given by the order of configured interfaces.
> An improved specification mechanism needs to be put in place before Cassandra 
> 5 is released.



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

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

Reply via email to