Customers will notice that when loading in records into a batch, the delete step is still triggered even if there are no records to delete. This step does add to processing time, and can be removed from the integration batch. If you are experiencing low performance because of these delete tasks, you can turn delete off in your routine integration batch jobs and create a dedicated delete job to handle deletes in the UI and special ETL requests. This KB article will show you how to remove the delete task from your batch, and how to create a separate delete job to handle deleted records.
...