Capacity Management - Content deployment limits

Limit	Maximum value	Limit type	Notes
Content deployment jobs running on different paths	20	Supported	For concurrently running jobs on paths that are connected to site collections in the same source content database, there is an increased risk of deadlocks on the database. For jobs that must run concurrently, we recommend that you move the site collections into different source content databases.   Note: Concurrent running jobs on the same path are not possible. If you are using SQL Server snapshots for content deployment, each path creates a snapshot. This increases the I/O requirements for the source database.