You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@lyra.org> on 2001/04/16 20:54:13 UTC
ooh... threaded cvs2svn
Bill Tutt sent me a little tongue-in-cheek ICQ about operating cvs2svn
asynchronously, so we can take advantage of multiprocessor machines :-)
In all seriousness, though, if we get compute bound, then multiprocessing
would be great. We can easily use threads for the create/load of a
transaction (if they're non-conflicting). A main thread would need to
sequence committing them, however.
[ that non-conflicting would be a bitch, but ya never know... with the right
preflight analysis, then store the result in the log, we could probably
leave flags in the log saying "parallelizable" ]
We'll see what happens. Python has great threading support, so it wouldn't
be a problem if it came to that.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: ooh... threaded cvs2svn
Posted by Chip Salzenberg <ch...@valinux.com>.
According to Greg Stein:
> In all seriousness, though, if we get compute bound, then multiprocessing
> would be great.
Please don't do that. Repository tools must be reliable; repository
*conversion* tools must be bulletproof. Threading adds to complexity,
which makes the likelihood of bugs go up.
--
Chip Salzenberg - a.k.a. - <ch...@valinux.com>
"We have no fuel on board, plus or minus 8 kilograms." -- NEAR tech