[Duplicity-tracker] [patch #6353] Concurrency for volume encryption and upload.

[Peter Schuller]

Follow-up Comment #10, patch #6353 (project duplicity):

I am attaching a slightly tweaked version that now has a proper option
(--asynchronous-upload) which is documented (as EXPERIMENTAL) in the man page,
and various other minor changes.

I now consider it good enough to request that it be considered for commit.

The only known, to me, outstanding outright possible bug is the way it stores
a backtrace from one thread and re-raising it in another.

I know there are some issues with this, and some frameworks have tackled it.
I suspect part of it has to do with Python code that is written to assume
ref-counting, and that retaining a stack frame affects the life-time of
objects. There may be other issues. This is the primary reason why I have
explicity marked it as "EXPERIMENTAL" in the man page.

Other people may have more input, and I might spent more time looking for
information on this. But I think it's worth getting committed for now, if only
to make it easier for willing people to test it.

As comments in the source indicates, this only enables asynchronous uploads
with a concurrency of 1, because > 1 also requires that we fix the various
backends as per my originally suggested plan on the duplicity list.


(file #16216)
    _______________________________________________________

Additional Item Attachment:

File name: duplicity_asyncupload.patch    Size:24 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?6353>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/