[
https://issues.apache.org/jira/browse/SAMZA-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221490#comment-14221490
]
Chris Riccomini commented on SAMZA-421:
---------------------------------------
So, I ran again. This time, 4GB heap, 1,000,000,000 messages processed. Job ran
at ~600k msgs/sec (different laptop), and ran for ~30 minutes. Job finished
fine, and did not run out of memory or have significant memory pressure.
I then did the same thing, but attached VisualVM. I ran for > 5 minutes, and
started doing heap dumps. There was almost no usage from the ConcurrentSkipList
data structure that I could find (~10 MB). Given that updateTimer is called for
every process() call, I expected to see more memory usage. Maybe [~closeuris]
can comment as to why I don't. If I'm doing 600k messages/sec, and the timer is
holding 5 minutes worth of data in memory, I should see hundreds of megs of
usage.
> Test the performance before and after adding the Timer metric
> -------------------------------------------------------------
>
> Key: SAMZA-421
> URL: https://issues.apache.org/jira/browse/SAMZA-421
> Project: Samza
> Issue Type: Test
> Components: metrics
> Reporter: Yan Fang
> Assignee: Yan Fang
> Labels: newbie
> Attachments: testTimer1.png, update-timer-speed.png
>
>
> As
> [recommended|https://issues.apache.org/jira/browse/SAMZA-349?focusedCommentId=14128365&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14128365]
> by Martin in SAMZA-349, it's worth testing the performance before and after
> implementing the Timer metric.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
