You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matt Stump (JIRA)" <ji...@apache.org> on 2015/02/19 22:05:12 UTC

[jira] [Updated] (CASSANDRA-8160) CF level option to call posix_fadvise for sstables on creation and startup

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

Matt Stump updated CASSANDRA-8160:
----------------------------------
    Attachment: trunk-8160.txt

Attaching my functional patch. I've been trying to find time to do performance testing to quantify gains if any, but haven't had time yet. Running into cassandra-stress bugs when attempting to use a custom yaml on cstar-perf. Haven't had time to run it down. 

> CF level option to call posix_fadvise for sstables on creation and startup
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8160
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8160
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Matt Stump
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 2.1.4
>
>         Attachments: trunk-8160.txt
>
>
> We should have a CF level configuration with will result in posix_fadvise being called for sstables for that CF. It should be called on node startup and for new sstables. This should be configurable per CF to allow for some CFs to be prioritized above others. Not sure if we should use POSIX_FADV_SEQUENTIAL or POSIX_FADV_WILLNEED. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)