Transformation job takes way longer when run on its own
I've noticed I have one job, TransformationJobX, where when I run it as part of a scheduled job that also runs many other jobs, it consistently takes about 3-4 minutes to run.
But when I am just doing development/testing, and I run TransformationJobX on its own, it consistently takes about 30 minutes to run! Weird.
As far as I can tell, all other things are the same. Same "environment." No other jobs running concurrently. Same starting conditions -- it truncate a table and then loads about 500,000 rows from scratch. The table is very wide, with many columns, including many text columns.
Any idea why it takes so long when I run it own its own, compared to when it's run in a sequence with many other jobs? (And, can I make it faster when I run it on its own?)