[
https://issues.apache.org/jira/browse/FLUME-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118416#comment-14118416
]
Hari Shreedharan commented on FLUME-2450:
-----------------------------------------
[~gmalouf] - Did you try a build with this patch? What kind of performance did
you see?
The faster alternative I can see is the one that use direct memory instead of
mmap - though I can't be sure how much faster it would be. My guesstimate would
be that this is reasonably fast as most of these ops would take place in page
cache and not on the fs.
The direct memory one is tricky since the user has to start the application
with more direct memory. Even if we check if there is enough direct memory at
the time of replay start, it is difficult to be sure there is enough as the
replay goes on, since there could be multiple file channels replaying at the
same time.
> Improve replay index insertion speed.
> -------------------------------------
>
> Key: FLUME-2450
> URL: https://issues.apache.org/jira/browse/FLUME-2450
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.6.0
>
> Attachments: FLUME-2450.patch
>
>
> Insertion into the replay index can take long sometimes because we use a file
> based index and tree set. We should switch this out for a memory mapped db
> and a hash set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
