[
https://issues.apache.org/jira/browse/STORM-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15160219#comment-15160219
]
ASF GitHub Bot commented on STORM-1571:
---------------------------------------
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1143#issuecomment-188092004
Given that the timing is measured only in the fill call, which happens per
batch of messages, the relative performance improvement is very low. By the
way, call could return in 1ms if fetch size is configured at a lower value for
better latency.
> Improvment Kafka Spout Time Metric
> ----------------------------------
>
> Key: STORM-1571
> URL: https://issues.apache.org/jira/browse/STORM-1571
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-kafka
> Affects Versions: 0.9.3, 0.9.4, 0.9.5, 0.9.6
> Environment: Mac 10.11.1 JDK 1.8.0_40
> Reporter: darion yaphet
> Assignee: darion yaphet
> Priority: Minor
> Attachments: 0001-Improvment-Kafka-Spout-Time-Metric.patch,
> 0002-Update-time-interval-counting-on-TridentKafkaEmitter.patch
>
>
> Use System.currentTimeMillis() to calculation time interval is better than
> System.nanoTime()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
