From 979159dcb413de79d45f0a2e4e20d14297b5f89d Mon Sep 17 00:00:00 2001 From: Andre Noll Date: Thu, 27 Aug 2015 18:08:02 +0200 Subject: [PATCH] migration: Remove item about scalability. Again, these points were already addressed earlier. --- manuals/en/main/migration.tex | 7 ------- 1 file changed, 7 deletions(-) diff --git a/manuals/en/main/migration.tex b/manuals/en/main/migration.tex index cd99db2..5e2eff2 100644 --- a/manuals/en/main/migration.tex +++ b/manuals/en/main/migration.tex @@ -141,13 +141,6 @@ \section{Important Migration Considerations} referenced in the Migration Job to define the Pool into which the data will be migrated. -\item Pay particular attention to the fact that data is migrated on a Job - by Job basis, and for any particular Volume, only one Job can read - that Volume at a time (no simultaneous read), so migration jobs that - all reference the same Volume will run sequentially. This can be a - potential bottle neck and does not scale very well to large numbers - of jobs. - \item Only migration of Selection Types of Job and Volume have been carefully tested. All the other migration methods (time, occupancy, smallest, oldest, ...) need additional testing.