slow job scheduled windows task

[gcurato82]

hello everyone, I use Talend open studio 7.3.1 and 

I have a problem with my work when it is scheduled with a windows task, because this is slow and takes a long time to run, while if I run it directly from Talend, the work is fast.

the ETL provides a tDBInput object -> tDBOutput, (database postgres) in the input the query retrieves 190 fields and there are 2 joins, are moved less than 400k records.

Does anyone have suggestions on how to fix my problem? 

[Anonymous]

It looks like I was writing my response as you were writing yours @Giuseppe Curato​. Can you add logging to all of your jobs that are running in this sequence. As suggested in my previous post. Just a start and end time, maybe to a DB table somewhere. This is actually a good idea when running jobs without using our subscription product (where this sort of thing is built in). From this you will be able to see precisely which job is causing this.

[gcurato82]

the log tracking is already active, there are no overlapping tasks, but if I run the task that is in trigger takes 3h, what I run now with precise time took a few minutes. I don’t understand the difference between the two tasks

[Anonymous]

What is the task before this runs doing? Have you tried to run this task on its own (with nothing else running), using the scheduler?

[gcurato82]

Yes, I have already tried to run the task manually and the result is always 3h. creating a new task scheduled to a precise time, it took a few minutes. in both cases, the server was unloaded

[Anonymous]

This is getting a bit confusing to follow. Can you confirm or correct the following statements.....

1. The job run through Talend Studio is quick
2. The job run through the scheduling tool (with other jobs being triggered or business as usual) takes 3 hours
3. The job run via the .bat file on the command line takes 3 hours
4. The job run from the scheduling tool on its own with no other jobs takes 3 hours

Once we have an understanding of the above, we can look at potential causes. I don't believe this is a Talend issue though.

[gcurato82]

Hi everyone, after doing several tests with tasks and jobs, I came to the conclusion that maybe the problem was related to the previous job that engages the database, so I solved by inserting a timer at the beginning of the job in trigger to postpone the start. I have so solved.