Re: [imapsync] multiple instances ok?

[Gilles LAMIRAL <gilles dot lamiral at laposte dot net>]

Hi Christopher and Josh,

> imapsync is pretty good about managing memory but  be aware that this is most likely the resource you will stress the most.

With latest Mail::IMAPClient.pm memory should not be a issue anymore but parallel runs have to take a look at it.

> Folder lists, message 'signatures',  etc. are stored in memory so the size of the process will be governed somewhat by the size (number of messages)
> and the complexity (number of folders) of the mailbox.

It should be only governed only by the biggest folder since imapsync loops and reuse memory per folder.

> I ended up making sure each imapsync process had its own working directory to write to and I explicitly set '--tmpdir' and '--pidfile' to avoid any conflicts.

In fact it will conflict only if you use them outside imapsync because imapsync doesn't care about them,
concurrency might be ok with the same values, just fake warnings.

> You might want to check out something like GNU's 'parallel' utility to drive your migration processes.
> This utility keeps N jobs running concurrently.  It draws from a list of shell commands to run and makes sure N are always running.

"xargs -P" is easy and can do the parallel work very well too.
You have many good choices.


--
Au revoir,                             09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06