Speed issue?

[nicoska84]

I'm experiencing a very slow upload speed compared to my actual/real upload speed.
That's Backblaze own performance check:

Here are my actual speed on the container running Backblaze:

This is the same docker instance running an iperf3 test:

So, it seems like the Backblaze container is "capped". Or could it be Backblaze? Now it's more than 1 week of 24/7 running.

Edit: I've also done a "Check Your Home Bandwith" test provided by Backblaze, and those are the results:

[HarletKing]

Backblaze's FAQ warns against setting your thread count above your actual thread count (or even equal to actual thread count). Try setting it to ~80% of your actual and see if that fixes it.

[nicoska84]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.

This is same connection, same hard drives, only run in a VM

[arko-pl]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.

This is same connection, same hard drives, only run in a VM

I don't think they're detecting wine. I think wine doesn't support something and speed is lowered down. I have the same issue on physical machine with Windows 7. Version 9.0.0.749 is the last with fine speeds, but a few weeks ago I tried to recover one file and it was missing in the restore tool. Then I discovered that almost 4 TiB of data is missing. I updated the BB and now I'm still suffering from low speeds. Maybe someone have any idea how to "debug" it or have a win7 machine that runs with good speeds?

[nicoska84]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.

This is same connection, same hard drives, only run in a VM

I don't think they're detecting wine. I think wine doesn't support something and speed is lowered down. I have the same issue on physical machine with Windows 7. Version 9.0.0.749 is the last with fine speeds, but a few weeks ago I tried to recover one file and it was missing in the restore tool. Then I discovered that almost 4 TiB of data is missing. I updated the BB and now I'm still suffering from low speeds. Maybe someone have any idea how to "debug" it or have a win7 machine that runs with good speeds?

Look here: #186 (comment)

[arko-pl]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.
This is same connection, same hard drives, only run in a VM

I don't think they're detecting wine. I think wine doesn't support something and speed is lowered down. I have the same issue on physical machine with Windows 7. Version 9.0.0.749 is the last with fine speeds, but a few weeks ago I tried to recover one file and it was missing in the restore tool. Then I discovered that almost 4 TiB of data is missing. I updated the BB and now I'm still suffering from low speeds. Maybe someone have any idea how to "debug" it or have a win7 machine that runs with good speeds?

Look here: #186 (comment)

I read this thread already. Old .749 version also has code that checked if running on wine. What I see is different the new client uses different API to upload and maybe the number of threads is the problem. On both versions number of threads doesn't exceed 10 regardless of settings. The message in logs says:
bztransmit25.log:2025-08-25 06:18:30 1304 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, but more than 30 GBytes of RAM, capping to 200 threads maxWinEleven64

[nicoska84]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.
This is same connection, same hard drives, only run in a VM

I don't think they're detecting wine. I think wine doesn't support something and speed is lowered down. I have the same issue on physical machine with Windows 7. Version 9.0.0.749 is the last with fine speeds, but a few weeks ago I tried to recover one file and it was missing in the restore tool. Then I discovered that almost 4 TiB of data is missing. I updated the BB and now I'm still suffering from low speeds. Maybe someone have any idea how to "debug" it or have a win7 machine that runs with good speeds?

Look here: #186 (comment)

I read this thread already. Old .749 version also has code that checked if running on wine. What I see is different the new client uses different API to upload and maybe the number of threads is the problem. On both versions number of threads doesn't exceed 10 regardless of settings. The message in logs says:
bztransmit25.log:2025-08-25 06:18:30 1304 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, but more than 30 GBytes of RAM, capping to 200 threads maxWinEleven64

You are suggesting that on Windows 7 version they're capping the threads?
Or that in the new app, regardless of the OS version, the threads are capped?

[arko-pl]

I don't think that's the cause. I believe that they can understand if a client run in Wine environment, and they're capping the speed.
This is same connection, same hard drives, only run in a VM

I don't think they're detecting wine. I think wine doesn't support something and speed is lowered down. I have the same issue on physical machine with Windows 7. Version 9.0.0.749 is the last with fine speeds, but a few weeks ago I tried to recover one file and it was missing in the restore tool. Then I discovered that almost 4 TiB of data is missing. I updated the BB and now I'm still suffering from low speeds. Maybe someone have any idea how to "debug" it or have a win7 machine that runs with good speeds?

Look here: #186 (comment)

I read this thread already. Old .749 version also has code that checked if running on wine. What I see is different the new client uses different API to upload and maybe the number of threads is the problem. On both versions number of threads doesn't exceed 10 regardless of settings. The message in logs says:
bztransmit25.log:2025-08-25 06:18:30 1304 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, but more than 30 GBytes of RAM, capping to 200 threads maxWinEleven64

You are suggesting that on Windows 7 version they're capping the threads? Or that in the new app, regardless of the OS version, the threads are capped?

Maybe I wasn't clear. My Windows 7 machine has only 4 GB of RAM, so there is "hardcoded" thread limit, but the speed for a single thread was 5 times faster on .749 version.

[arko-pl]

I did some additional research and there is a logic that checks system overhead before spawning new threads and this logic doesn't work well on wine. I ran several ffmpeg hevc compression threads, wine compilation in parallel and backblaze started to spawn more threads. I got 21 threads maximum and reach about 11 MB/s network utilization. I hope it will help you in further investigations.