[
https://issues.apache.org/jira/browse/SAMZA-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854689#comment-13854689
]
Chris Riccomini commented on SAMZA-111:
---------------------------------------
For the record, in SAMZA-111.0.png, the window (15.9%), commit (13%), and send
(10.4%) are all logging as well. I just couldn't fit it in the screenshot. This
combines for 39.3% of the total CPU time in the main process loop. On top of
this, window, commit, and send are entirely no-ops. Clearly there are more
gains to be had here.
> SystemConsumers is slow with large partition count
> --------------------------------------------------
>
> Key: SAMZA-111
> URL: https://issues.apache.org/jira/browse/SAMZA-111
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Attachments:
> 12-threads-1000-streams-4-partitions-each-with-hacky-fix.png,
> 12-threads-1000-streams-4-partitions-each.png,
> 12-threads-8-streams-4-partitions-each.png, SAMZA-111.0.patch,
> SAMZA-111.0.png, samza-perf-hacks.0.diff, samza-perf-hacks.png
>
>
> We have been seeing very slow processing speed when running a Samza container
> that consumes from 1000s of partitions. We don't see a corresponding slow
> speed when running the same code, but with fewer input partitions (say 8-24).
> The messages per second seems to drop off as more partitions are added to the
> Samza container. One Samza job has ~2500 partitions, and is seeing only 6000
> messages/sec. The same code running with ~9 partitions is seeing 30,000
> messages/sec.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
