The amount of time needed to complete the import process is influenced by several factors.
For example, the amount of data, the number of mails (files) to be imported, networkconnection (network throughput), the speed of the processor and hard drive of the computers on which the import takes place and the computere where the mails are to be imported from.
It is recommended to use the local disc of the import computer to provide storage for the Import Container and the workspace.
When the import process has finished, the container can then be moved to its final storage destination.
The speed of the processor plays the most important role in the time it takes to complete the import process.
A processor with multiple cores will greatly increase how fast the process finishes.
The MailDepot Importer will display the progress of the task, or import, after the first mails have been imported.
Example of a network import
The mails files were imported from a CIFS-Share with a network connection speed of 100 Mbit/second, while the MailDepot and workspace were stored locally.
Hardware: Intel 4 Kernel CPU Xeon (NetBurst), 4 GB RAM, RAID 5 with 6 SAS Drives
Amount: 1 Million Mails
Import Method: File-Import
Time needed: 27 hours 45 minutes
Speed: 10 Mails / Second
Example of a local import
The mail files were imported via an PST, while the PST, the MailDepot and workspace were stored locally.
Hardware: Intel i5-7300HQ @2.5ghz, 24 GB RAM, NVME SSD
Amount: 1 Million Mails
Import-Methode: PST-Import
Time needed: 12h 40m
Speed: 22 Mails / Second
Example of a local import - with better hardware
The mail files were imported via an PST, while the PST, the MailDepot and workspace were stored locally.
Hardware: Intel i7-7700T @2.9ghz, 64 GB RAM, NVME SSD
Amount: 1 Million Mails
Import-Methode: PST-Import
Time needed: 8h 57m
Speed: 31 Mails / Second