You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Israel Ekpo (JIRA)" <ji...@apache.org> on 2013/03/27 06:33:16 UTC

[jira] [Updated] (FLUME-1071) Evaluate performance of AVRO source with multiple clients

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

Israel Ekpo updated FLUME-1071:
-------------------------------

    Issue Type: Improvement  (was: Task)
    
> Evaluate performance of AVRO source with multiple clients
> ---------------------------------------------------------
>
>                 Key: FLUME-1071
>                 URL: https://issues.apache.org/jira/browse/FLUME-1071
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.2.0
>         Environment: CentOS 6.2 64-bit
>            Reporter: Will McQueen
>             Fix For: v1.4.0
>
>
> I ran an AVRO stress test with 10 avro clients continuously sending data. Those clients all target the same port.
> A profiling run (pict att'd) shows that the 10 worker threads are waiting a lot (yellow) and little time spent running (green).
> One thing to try for future tests, as a basis for comparison, would be to use an increased heap size because in general flume should give better performance with more mem.
> Note that a source's performance will likely depend on the channel in use (I'm using memory channel in this case), since the transactions are the primary thing that can effect blocking.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira