[ 
https://issues.apache.org/jira/browse/GOBBLIN-1824?focusedWorklogId=860181&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-860181
 ]

ASF GitHub Bot logged work on GOBBLIN-1824:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/May/23 20:52
            Start Date: 02/May/23 20:52
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 commented on code in PR #3686:
URL: https://github.com/apache/gobblin/pull/3686#discussion_r1183040061


##########
gobblin-data-management/src/main/java/org/apache/gobblin/data/management/copy/ManifestBasedDataset.java:
##########
@@ -117,6 +126,7 @@ public Iterator<FileSet<CopyEntity>> 
getFileSetIterator(FileSystem targetFs, Cop
         CommitStep step = new DeleteFileCommitStep(targetFs, toDelete, 
this.properties, Optional.<Path>absent());
         copyEntities.add(new PrePublishStep(datasetURN(), Maps.newHashMap(), 
step, 1));
       }
+      log.info(String.format("Workunits calculation took %s milliseconds to 
process %s files", System.currentTimeMillis() - startTime, numFiles));

Review Comment:
   I don't have a strong preference here, but calling nanoTime seems a little 
expansive. Also, in this case, where our computing time usually takes several 
seconds to several minutes, do we need that precise value? 





Issue Time Tracking
-------------------

    Worklog Id:     (was: 860181)
    Time Spent: 1h 40m  (was: 1.5h)

> Improving the Efficiency of Work Planning in Manifest-Based DistCp Jobs
> -----------------------------------------------------------------------
>
>                 Key: GOBBLIN-1824
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1824
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Optimizing Permission Calculation and Introducing Multithreading in 
> Manifest-Based DistCp Work Planning



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to