[Cyberduck-trac] [Cyberduck] #10990: Cyberduck really slow with Onedrive cryptomator vault (was: Cyberduck really slow with Onedrive cryptomat container)
Cyberduck
trac at cyberduck.io
Wed Mar 11 11:50:09 UTC 2020
#10990: Cyberduck really slow with Onedrive cryptomator vault
------------------------+----------------------
Reporter: Jeroen1000 | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: core | Version: 7.2.4
Severity: normal | Resolution:
Keywords: | Architecture: Intel
Platform: Windows 10 |
------------------------+----------------------
Description changed by Jeroen1000:
Old description:
> Hi dev's and fellow users,
>
> I wanted to use Cyberduck to sync an online only (unlocked) Cryptomat
> vault into backup storage. So an actual copy of the file, not just a
> placeholder, is saved to this backup storage. Online only storage is not
> considered a backup.
>
> Anyway, indexing the files (around 10k) seems to take forever. I
> interrupted the process after half an hour, noticing not a single file
> had been synced.
>
> When I let Onedrive itself sync the (encrypted) vault folders, it starts
> saturating a 200 megabit internet connection in under 10 minutes. At that
> speed the process gets completed well before Cyberduck has finished the
> indexing step. But this is undesired as I do not want a local copy of the
> encrypted files.
>
> Is this expected behaviour because to me it feels like abnormally
> sluggish?
>
> Best regards,
> Jeroen
New description:
Hi dev's and fellow users,
I wanted to use Cyberduck to sync an online only (unlocked) Cryptomator
vault into backup storage. So an actual copy of the file, not just a
placeholder, is saved to this backup storage. Online only storage is not
considered a backup.
Anyway, indexing the files (around 10k) seems to take forever. I
interrupted the process after half an hour, noticing not a single file had
been synced.
When I let Onedrive itself sync the (encrypted) vault folders, it starts
saturating a 200 megabit internet connection in under 10 minutes. At that
speed the process gets completed well before Cyberduck has finished the
indexing step. But this is undesired as I do not want a local copy of the
encrypted files.
Is this expected behaviour because to me it feels like abnormally
sluggish?
Best regards,
Jeroen
--
--
Ticket URL: <https://trac.cyberduck.io/ticket/10990#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list