[
https://issues.apache.org/jira/browse/CAMEL-13414?focusedWorklogId=226723&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-226723
]
ASF GitHub Bot logged work on CAMEL-13414:
------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Apr/19 15:22
Start Date: 12/Apr/19 15:22
Worklog Time Spent: 10m
Work Description: bd2019us commented on pull request #2868: CAMEL-13414
use System.currentTimeMillis()
URL: https://github.com/apache/camel/pull/2868
new Date() is just a thin wrapper around System.currentTimeMillis(). Using
System.currentTimeMillis() can help avoid to create a new Date object and the
system can speed up
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 226723)
Time Spent: 10m
Remaining Estimate: 0h
> Date.getTime() can be changed to System.currentTimeMillis()
> -----------------------------------------------------------
>
> Key: CAMEL-13414
> URL: https://issues.apache.org/jira/browse/CAMEL-13414
> Project: Camel
> Issue Type: Bug
> Reporter: bd2019us
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello,
> I found that System.currentTimeMillis() can be used here instead of new
> Date.getTime().
> Since new Date() is a thin wrapper of light method
> System.currentTimeMillis(). The performance will be greatly damaged if it is
> invoked too much times.
> According to my local testing at the same environment,
> System.currentTimeMillis() can achieve a speedup to 5 times (435 ms vs 2073
> ms), when these two methods are invoked 5,000,000 times.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
