GitHub user EricTonissen added a comment to the discussion: Performance HOP on 
Linux

I am not sure whether I can agree.

I suppose that the startup from HOP is finished before the logging of 'Start of 
workflow execution'.
The same is the startup from Pentaho before the logging of 'Start of job 
execution'.

Below is the logging from both HOP and Pentaho.

It takes now more time than in previous compare, because there is more data to 
process.
But they both process same data, doing the same things, and both gives same 
results.
Both processes running on same machines, same memory parameters, and so on.
Only different java version, as mentioned before.
And running several times this processes, they all give the similar results.

2025/12/08 12:17:10 - HopRun - Enabling project 'eridani'
2025/12/08 12:17:10 - HopRun - Starting workflow: 
/opt/hop/eridani-base/pdi-repo/jobscheduler/scheduler/util/jb_scheduler_report.hwf
**2025/12/08 12:17:10 - jb_scheduler_report - Start of workflow execution**

2025/12/08 12:17:35 - jb_scheduler_report - Finished action [Report queue] 
(result=[true])
**2025/12/08 12:17:35 - jb_scheduler_report - Workflow execution finished**
2025/12/08 12:17:35 - jb_scheduler_report - **Workflow duration : 24.867** 
seconds [ 24.867" ]


2025/12/08 12:15:58 - Kitchen - Logging is at level : Basic
2025/12/08 12:15:58 - Kitchen - Start of run.
2025/12/08 12:15:58 - RepositoriesMeta - Reading repositories XML file: 
/home/eridanivriend/.kettle/repositories.xml
**2025/12/08 12:16:01 - jb_scheduler_report - Start of job execution**

**2025/12/08 12:16:16 - jb_scheduler_report - Job execution finished**
2025/12/08 12:16:16 - Kitchen - Finished!
2025/12/08 12:16:16 - Kitchen - Start=2025/12/08 12:16:01.876, Stop=2025/12/08 
12:16:16.916
2025/12/08 12:16:16 - Kitchen - **Processing ended after 15 seconds.**


GitHub link: 
https://github.com/apache/hop/discussions/6116#discussioncomment-15195456

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to