Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Performance falls if OSGI job is deployed

Hello everybody

 

I've got some problem using an OSGI job.

I've developed a job whitch has to receive an xml file, transform data, send data to SOAP service, receive back the data, transform them again and finally responce! see capture1.jpg

 

If I run the job on "Open Studio", it works fine taking not too much time!

If I deploy the service as OSGI, the performances falls down.

50% of the requestes works but taking 3 times more time than in Studio, the rest of the requestes takes longer than result in a time out.

 

Could someone please suggest what to check or change in order to avoid performance falls!

 

thanks in advance

 

Muzio

 

Labels (2)
15 Replies
Anonymous
Not applicable
Author

Hello,

Could you please indicate on which build version you got this issue? Are you using the same version for your studio and runtime?

Best regards

Sabrina

 

Anonymous
Not applicable
Author

Hello Sabrina

 

Sorry for the delay..

I'm working on 6.3.0.20161026_1219 Open Studio Verision.

I've got some problems to identify which RunTime version i'm working on!

I always suppose to be the same than the studio....

 

Could you please help me to identify the RunTime version?

Anonymous
Not applicable
Author

Hello Sabrina

Sorry for the delay..
I'm working on 6.3.0.20161026_1219 Open Studio Verision.
I've got some problems to identify which RunTime version i'm working on!
I always suppose to be the same than the studio....

Could you please help me to identify the RunTime version?
Anonymous
Not applicable
Author

Can someone give me a help please!!! Since august i'm running 2 of those ws in debug mode....
How it's possible debug services are much more faster than
Anonymous
Not applicable
Author

Hello,

Sorry for delay!

Could you please use info to check your talend runtime build version?

Is there any error message in runtime log? Which is located in <runtime>\containber\log\tesb.log

With talend open source, the runtime basically allows you to use the same JVM, which means that they essentially share the same memory.

For your scenario, you can use the cron tab (Linux) or a scheduler (Windows) to start your DI Jobs, and use the ESB Runtime to run just services and routes. 

 

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi Sabrina

 

 

Could you please use info to check your talend runtime build version?

 


Sorry Sabrina... i really feel myself like an idiot... but no way to find a "info" anywhere.

 

At the moment, with de deployed version seams to not exist anymore the timeout problem.

But the performance still falls.

 

thank you

 

see log file 

 

 


tesb.log
Anonymous
Not applicable
Author

I forgot to give you the percentage..
Deployed job 56 seconds
Debug job 23 seconds

100% slower
Anonymous
Not applicable
Author

double sorry...

 

service name is ISAPRO_cSAP_IN_OrderSimulation

 

thanks again

Anonymous
Not applicable
Author

Hello,

Have you tried to use the cron tab (Linux) or a scheduler (Windows) to start your DI Jobs to see if the performance is better?

With talend open source for ESB, there is no job server you can use.

Best regards

Sabrina