S3Drive - Navigating mounted drive on S3 slower than on rclone (same bucket)

Hi! Basically, when using the S3 version of the same bucket, it is slower to navigate than on rclone. (Clicking folders just takes forever to load; opposite of when using rclone). However, navigation on the application itself (not on the mounted folder) remains the same speed (fast). I tried setting vfs cache to minimal to no avail.

Jian

Hi! Basically, when using the S3 version of the same bucket, it is slower to navigate than on rclone. (Clicking folders just takes forever to load; opposite of when using rclone). However, navigation on the application itself (not on the mounted folder) remains the same speed (fast). I tried setting vfs cache to minimal to no avail.

Hi, my understanding is that you find disk drive mount slower to navigate comparing to the S3Drive UI, is that correct? Are you using managed S3 account or external S3? Have you configured S3 credentials under the S3 tab or under the Rclone tab? Thanks!

Yes, looking at the network tab in task manager when loading a S3 mounted folder, it uses <0.1 mbps, making it stuck loading perpetually. Meanwhile, using the rclone version of the same account uses the full capacity of my network. But navigating through the app works fine and fast regardless of S3 or rclone usage. For the S3, I connect it with my Backblaze B2 account.

Jian

Yes, looking at the network tab in task manager when loading a S3 mounted folder, it uses <0.1 mbps, making it stuck loading perpetually. Meanwhile, using the rclone version of the same account uses the full capacity of my network. But navigating through the app works fine and fast regardless of S3 or rclone usage. For the S3, I connect it with my Backblaze B2 account.

Meanwhile, using the rclone version of the same account

I assume that once you configure Backblaze through Rclone tab, you're probably doing it using native Backblaze integration: https://rclone.org/b2/ and that's also what's being used for the mount. When you configure Backblaze using S3 credentials and login to S3Drive, then the mount you create utilizes S3 configuration: https://rclone.org/s3/#configuration In such case there are two different implementations which might make some performance difference... however: it uses <0.1 mbps, making it stuck loading perpetually. this shouldn't happen regardless if it's S3 or B2. We're going to try configuring Backblaze bucket and try Rclone mount. Can you let us know if you have Server-Side encryption and/or versioning enabled for your bucket on Backblaze? (edited)

Tom

Meanwhile, using the rclone version of the same account

I assume that once you configure Backblaze through Rclone tab, you're probably doing it using native Backblaze integration: https://rclone.org/b2/ and that's also what's being used for the mount. When you configure Backblaze using S3 credentials and login to S3Drive, then the mount you create utilizes S3 configuration: https://rclone.org/s3/#configuration In such case there are two different implementations which might make some performance difference... however: it uses <0.1 mbps, making it stuck loading perpetually. this shouldn't happen regardless if it's S3 or B2. We're going to try configuring Backblaze bucket and try Rclone mount. Can you let us know if you have Server-Side encryption and/or versioning enabled for your bucket on Backblaze? (edited)

Yes, that's correct! I have versioning enabled but encryption is disabled