[
https://issues.apache.org/jira/browse/HIVE-21611?focusedWorklogId=492975&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-492975
]
ASF GitHub Bot logged work on HIVE-21611:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Sep/20 14:10
Start Date: 30/Sep/20 14:10
Worklog Time Spent: 10m
Work Description: belugabehr closed pull request #595:
URL: https://github.com/apache/hive/pull/595
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 492975)
Time Spent: 1h 40m (was: 1.5h)
> Date.getTime() can be changed to System.currentTimeMillis()
> -----------------------------------------------------------
>
> Key: HIVE-21611
> URL: https://issues.apache.org/jira/browse/HIVE-21611
> Project: Hive
> Issue Type: Bug
> Reporter: bd2019us
> Assignee: Hunter Logan
> Priority: Major
> Labels: pull-request-available
> Attachments: 1.patch
>
> Time Spent: 1h 40m
> 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
(v8.3.4#803005)
