Job generation from Talend Administration Console = SLOW

[Anonymous]

Hi,
I did several Talend projects, running on both Linux and Windows systems and everytime I notice that job generation from the Talend Administration Console takes way more time and cpu power then building or exporting the job from the Studio. This is not 2x, but more like 500x times slower.
Anyone also experienced this behaviour? and how to solve?
Thanks!

[Anonymous]

Hi,

I am also facing the same issue while generating it is taking more time. Please give any suggestion.

Please give us more description about your current situation.(job design, talend product version...).
Best regards
Sabrina

[Stephen_Elves1]

Yep same here using 5.4.1 much, much faster to generate and run in Studio (on an ordinary desktop machine) than via TAC or CommandLine (on a powerfull server) which take approximately them same, never more then 15 minutes or so but still very odd.

[Anonymous]

Hi Sabrina,
I have attached the images herewith with main job and the one subjob. There are similar 3 more subjobs in it. It is giving issue when running from Windows Service.

[Anonymous]

oh the above one is only the sub job
due to pixel problem the main job can't be posted.

[Anonymous]

I have again attached the mainjob

[Anonymous]

Hi Sabrina
Sorry for uploading lots of comments. But i could not post the main job, anyway the main job only transfers some file here-and-to. And gets the response from the sub jobs which I have already posted,
Can u plz give the solution??

[Anonymous]

Hi,
I have seen your pic and found there is tRunjob component in your workflow. Have you checked out option "Use an independent process to run subjob" which use an independent process to run the subjob. This helps in solving issues related to memory limits.
TalendHelpCenter:tRunJob.
Best regards
Sabrina

[Anonymous]

Hi Sabrina,

I tried to make the sub-job independent but it gives some other issue. As we have used tBufferOutput Component in each subjob on making the job independent the value is not returned and we are given exception.
Thanks!!

[Anonymous]

I've tried using "Use an independent process to run subjob" it can help with memory issues whilst the job is running but does not seem to affect either the time to "generate" the job or the memory usage when doing so (i.e. the commandLine process that is generating the job can run out of java heap space).

[_AnonymousUser]

Hi,
I migrate from 5.3 to 5.4.1 r111943-20131212-1133, and i'am having trouble with an exported job.
That job works fine with 5.3, (TOS GUI and autonomous job) and with 5.4.1 it takes too much time to execute as an autonomous job.
If running in TOS GUI 5.4.1, it takes about 20mn to complete, but when running in autonomous job it is 1 or 2 hours !...
It is not a problem with TOS 5.3.
Have an idea ?
Thx