[jira] [Commented] (CASSANDRA-6759) CommitLogSegment should provide madvise DONTNEED hint after syncing a segment

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-6759:
-------------------------------------------

committed

> CommitLogSegment should provide madvise DONTNEED hint after syncing a segment
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6759
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6759
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 2.1 beta2
>
>         Attachments: 6759.txt
>
>
> This is a really simple change, copying what we do with SequentialWriter, but here we know for sure we don't intend to re-read the region again in the near future so it's definitely wasted file buffer space.
> I have a patch, but I would like to do some brief performance comparisons before submitting it, and see if providing DONTNEED at file creation like we do for SW is sensible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)