[
https://issues.apache.org/jira/browse/SAMZA-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200355#comment-14200355
]
Chris Riccomini commented on SAMZA-421:
---------------------------------------
bq. How many messages did you process during this profiling run?
100 million.
bq. My concern was that it would slow down or run out of memory when it has
collected 5 minutes worth of measurements (at 1M msgs/sec, that would be 300M
measurements).
Ah, yes that makes sense. Let me run it for longer. I did have to bump the heap
to 4G, but I've had to do that in the past as well (pre-updateTimer).
bq. but probably a couple of gigs
If it is indeed this size, then yes, that's a lot of memory overhead. I'd
mostly been focusing on CPU.
bq. The overhead wouldn't necessarily show up in RunLoop.process(), but also
when the metrics system periodically takes a snapshot of the measurements, and
in GC.
Will have a look at the metrics thread's CPU time.
It'll have to be tomorrow though. I'm away from my perf box today.
> 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)
