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

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
MarkM1
Contributor II
Contributor II
‎2020-12-28 10:07 AM

Poor Performance when using tStatCatcher

I have a long job with many sub-jobs. It takes about 300 seconds to execute. I wanted to collect some stats on the job and certain components, so I added a tStatCatcher component like this:

0693p00000AcRGxAAN.png

This makes the job take over 1000 seconds, and it appears that the stat Catcher starts and stops for each row written to the DB. I changed it to use a shared connection so it didn't have to make the connection each time, but that seems to have no effect. Is tStatCatcher just a bad component, or is there a way to make it perform better?

Labels (3)
Labels
205 Views
0 Likes
1 Reply
Anonymous
Not applicable
‎2020-12-29 12:07 AM

Hello,

What's the transformation are you using in your tMap? The Stats & Logs preferences can be set for all jobs in a project via Project Settings, or separately for individual jobs via the Job tab.

0693p00000AcWF6AAN.pngBest regards

Sabrina

205 Views
0 Likes