rejetto forum

Running HFS on Google Compute Engine, having bandwidth problems.

0 Members and 1 Guest are viewing this topic.

Offline Misterfriday

  • Occasional poster
  • *
    • Posts: 1
    • View Profile
Hello,
first of all I want to thank the developer(s) for providing such an amazing small tool to the general public. Thanks a lot for your effort, it's much appreciated.

Now to my problem. I'm running a render farm for my company on google compute engine and I've deployed HFS on a Google Compute Engine instance that has more than sufficient up and down bandwidth. Yet It seems that I can only get about 25 Mbits of download bandwidth when I'm downloading files. The downloads are VERY consistent at 25Mbits, so no sudden spikes or gaps. Just like its artificially capped.

At first I thought it's because of a restriction on googles side in regards of HTTP but it's not. For testing I've uploaded some files to "Wetransfer" and also did a regular internet connection speedtest and the instance has a whooping 3 gigabits of upload bandwidth. Uploads to Wetransfer via HTTP where also extremely fast. Only uploads via HFS seem to be capped at 25Mbits, I don't have any limits set in HFS(at least not that I'm aware of) and there are no firewall rules or artificial throttling set, no proxy, nothing.

Do you have any idea what this could cause? I really would like to use HFS for file transfers but I keep having these issues.

Thanks in advance
-Robert


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13510
    • View Profile
welcome Robert!
I never had the chance to make a test with a connection that fast.
I've reached 30mbps with my home connection, that was its limit, and 70mbps in a LAN.
HFS is not very fast any way. In the past I've spent only few days in optimizing its http engine.
The only idea coming to mind for your problem is: maybe it's high on CPU. HFS surely needs more CPU than other optimized softwares, and it will use only 1 core of the CPU, so you are capped by that. See if it tops one of the cores of the CUP.