Whether components are idle in a batch

edit

The reason for the behavior you're describing is that Data Collector tracks offsets for the origin. The offsets can't be safely committed until that batch is completely flushed (i.e. completed writing) by the destination(s).

That being said, there are likely various steps you can take to increase the efficiency of the pipeline you have screenshotted. First, the Jython evaluator (as with any scripting processor) is quite slow, so if any of its logic can be replaced by native processors, it should be much faster. Also, the JDBC multitable origin supports multithreaded partitioning, if the underlying table has a suitable structure (single numeric offset or key column).