Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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:
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?
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.
Sabrina