Avoid job parallelism when uploading to an encrypted folder
authorKevin Ottens <kevin.ottens@nextcloud.com>
Wed, 1 Jul 2020 12:12:18 +0000 (14:12 +0200)
committerKevin Ottens (Rebase PR Action) <er-vin@users.noreply.github.com>
Wed, 1 Jul 2020 17:11:57 +0000 (17:11 +0000)
commit5a07a36d06c26ea2943926ec8a2afe962a4f87d4
tree273ba277529d55c56f2fb279c0e7b93362214566
parent27b982ceafba8aa16397552619d907d02c5ae5d7
Avoid job parallelism when uploading to an encrypted folder

With the current design of the file upload this necessarily pushed to a
lock starvation on the folder. Indeed you could end up with N jobs
asking for the lock at the same time. So just avoid parallelizing for
now even though it will be slow.

We could try to optimize but that'd require some serious changes to the
sync logic on the jobs... let's stabilize first and optimize later.

Signed-off-by: Kevin Ottens <kevin.ottens@nextcloud.com>
src/libsync/propagateupload.cpp