hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-21611) Date.getTime() can be changed to System.currentTimeMillis()
Date Fri, 09 Oct 2020 00:53:00 GMT


ASF GitHub Bot logged work on HIVE-21611:

                Author: ASF GitHub Bot
            Created on: 09/Oct/20 00:52
            Start Date: 09/Oct/20 00:52
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] closed pull request #1334:


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:

Issue Time Tracking

    Worklog Id:     (was: 497682)
    Time Spent: 2h 20m  (was: 2h 10m)

> Date.getTime() can be changed to System.currentTimeMillis()
> -----------------------------------------------------------
>                 Key: HIVE-21611
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: bd2019us
>            Assignee: Hunter Logan
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: 1.patch
>          Time Spent: 2h 20m
>  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

This message was sent by Atlassian Jira

View raw message