[Question] Explain how sync between buckets work; slow overall speed

未关闭
  • 哪里不对？
#917 8 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
12/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
cloud, documentation

调研方向

The payload names no source files, tests or entry points, only the b2 sync command with its --threads, --delete and --replaceNewer flags. Start by reading the sync command's help output and the project docs to see what they say about how bucket-to-bucket sync works. Done would mean a written explanation of the sync process and its throughput limits, which requires maintainer input on the design.

由索引模型根据 Issue 内容生成。

描述

Problem

I have a sourceBucket with 30.000 images (50-100 KB each), roughly 1.4 GB storage in total, and I want to "sync" it from to a destinationBucket.

b2 sync --threads <10|100|500> --delete --replaceNewer b2://sourceBucket b2://destinationBucket

As this concern many files, or even a large filesize, I'm stumped that it takes 1.5 to 2 hours to complete. The output of the command above shows between 70-100 kB/s (deteriorating over time), which seems kind of low, even when I run this on a production server with 10 Gbps up/down.

Question

As it seems the network speed, or the amount of threads, don't really have much impact on the overall performance, so could you provide me answers on the following questions:

  1. How does sync between buckets work?
    • I cannot find in the documentation on how this works.
    • Does my environment e.g. network speed, system hardware, or other requirements have any influence on syncs between buckets.
  2. Why does it take so long to for a relatively small amount of files, of such a small size, to be synced to another bucket?
  3. What can be improved on my side to sync it faster?
    • I've already tried tweaking the threads argument, but it only differs in magnitude of +/- 10 kB/s.
主要语言
Python
星标
638
派生
138
平均合并
8 小时 27 分钟
30 天内合并 PR
8

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Backblaze/B2_Command_Line_Tool 的其他 Issue

查看 Backblaze/B2_Command_Line_Tool 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。