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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Tlogrow Components breaks down GUI Performance.

Talend Open Studio for Data Integration
Version: 6.3.1
Hello everybody 

I have an Bulk Job with Salesforce and everything works as expect.
But when i use some Tlog Rows for testing ( Records output are about 10 000) , the GUI Performance get's slowing down drastically with some hangups...
So i'm not really sure if this an normal behaviour  if you use an Bulk Job with Tlogrows outputs ?
My older SF-Jobs which are created without Bulk Components doesn't have these issue.
regard john   

Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

TRF is right. A nice way to redirect the the text from the output window to a file is shown in the tutorial below. Deactivating the tLogRows will still be quicker, but this method helps with the GUI slow down.
https://www.rilhia.com/quicktips/quick-tip-redirect-output-console-file

View solution in original post

6 Replies
TRF
Champion II
Champion II

Hi,
No link between Salesforce components and this behaviour, just due to the number of rows in the console.
Push your log to a file if needed.
Regards,
TRF
Anonymous
Not applicable
Author

TRF is right. A nice way to redirect the the text from the output window to a file is shown in the tutorial below. Deactivating the tLogRows will still be quicker, but this method helps with the GUI slow down.
https://www.rilhia.com/quicktips/quick-tip-redirect-output-console-file
Anonymous
Not applicable
Author

Hello 
Thanks for helping  

@rhall_2.0:
Works perfectly

regards john 
 
Anonymous
Not applicable
Author

@rhall_2.0:

additional Question:

is it possible to seperate the different tlog  rows from the output on the java log file easily ? 

maybe with some spaces and the component name from the tlog.

regards john  
Anonymous
Not applicable
Author

This shouldn't be difficult after the log file has been written. Doing it while the job is running is not going to be possible using this method. 
Anonymous
Not applicable
Author

ok 
thanks 

best regards john