You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@systemml.apache.org by "bd2019us (JIRA)" <ji...@apache.org> on 2019/04/12 15:49:00 UTC

[jira] [Updated] (SYSTEMML-2526) Date.getTime() can be changed to System.currentTimeMillis()

     [ https://issues.apache.org/jira/browse/SYSTEMML-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bd2019us updated SYSTEMML-2526:
-------------------------------
    Attachment: 1.patch

> Date.getTime() can be changed to System.currentTimeMillis()
> -----------------------------------------------------------
>
>                 Key: SYSTEMML-2526
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-2526
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: bd2019us
>            Priority: Major
>         Attachments: 1.patch
>
>
> src/main/java/org/apache/sysml/api/mlcontext/MLContext.java 337
> src/main/java/org/apache/sysml/api/mlcontext/MLContextUtil.java 1258
> 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)