3 ms·

In your experience, how's the speed with sending and receiving files this way? I have relatively little knowledge about IPFS right now, but the last time I trie

by godot 9y ago

In your experience, how's the speed with sending and receiving files this way? I have relatively little knowledge about IPFS right now, but the last time I tried to access a site that claimed to be hosted in IPFS (accessing it through a gateway), it was so slow that it failed to load.

StavrosK 9y ago
That is a constant source of frustration for us as well. We've been having problems where nodes intermittently couldn't discover other nodes, so content that was in one IPFS node would be unavailable on another. I've spoken to a few people from the IPFS team, but they couldn't figure out the cause. Hopefully the next version makes discovery more reliable and fixes this (the files are quite quick to download once peers discover each other).
- prophesi 9y ago
  Yeah, I have two IPFS nodes, and had to make sure their swarm was bootstrapped with the IP address of each other. And even then, I still sometimes have to `ipfs swarm connect [ip_address]` after a reboot to be able to discover the content they have pinned. Once they're connected, however, I haven't had any performance issues unless I was using IPNS. Though I only use IPFS to host static sites ( https://ipfs.poeti.codes/ipns/dreams.poeti.codes/ https://ipfs.poeti.codes/ipns/dreams.poeti.codes/ )
  - alexsicart 9y ago
    So, in a private ipfs network (connect to other peers who have a shared secret key) https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#private-networks https://github.com/ipfs/go-ipfs/blob/master/docs/experimenta.... All the IPFS nodes are connected by default? Each peer pin files from other peers?
    - StavrosK 9y ago
      No, if I understand correctly, he just bootstraps the nodes from each other, making sure they are initially strongly connected. I tried that too, but it didn't reliably help the problem.
      - prophesi 9y ago
        Yep, precisely! And if I'm having peer discovery issues with just two nodes, I can't imagine what you guys are having to go through. :/ For the curious: you'd run `ipfs id` on the nodes to get their addresses. Then you'd run `ipfs config edit` on them and add the other node's address to the bootstrap section. https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#bootstrap https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#b... But yeah... They'd still mysteriously not connect to each other at times.
        StavrosK 9y ago
        Yep :( It's pretty disheartening to work on a product for some time and have the underlying technology just not work up to your standard. Hearth is basically hit and miss for that reason, sometimes files show up right away and it's amazing, sometimes they time out and it's useless. Very frustrating, and there's absolutely nothing we can do about it.
        pookeh 9y ago
        I haven't looked at IPFS in depth but could this be because both the nodes are behind a nat and they need a relay node?
        StavrosK 9y ago
        No, at least one wasn't. Plus, this happened even when they were directly connected.

by godot 9y ago

StavrosK 9y ago

That is a constant source of frustration for us as well. We've been having problems where nodes intermittently couldn't discover other nodes, so content that was in one IPFS node would be unavailable on another. I've spoken to a few people from the IPFS team, but they couldn't figure out the cause. Hopefully the next version makes discovery more reliable and fixes this (the files are quite quick to download once peers discover each other).

prophesi 9y ago
Yeah, I have two IPFS nodes, and had to make sure their swarm was bootstrapped with the IP address of each other. And even then, I still sometimes have to `ipfs swarm connect [ip_address]` after a reboot to be able to discover the content they have pinned. Once they're connected, however, I haven't had any performance issues unless I was using IPNS. Though I only use IPFS to host static sites ( https://ipfs.poeti.codes/ipns/dreams.poeti.codes/ https://ipfs.poeti.codes/ipns/dreams.poeti.codes/ )
- alexsicart 9y ago
  So, in a private ipfs network (connect to other peers who have a shared secret key) https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#private-networks https://github.com/ipfs/go-ipfs/blob/master/docs/experimenta.... All the IPFS nodes are connected by default? Each peer pin files from other peers?
  - StavrosK 9y ago
    No, if I understand correctly, he just bootstraps the nodes from each other, making sure they are initially strongly connected. I tried that too, but it didn't reliably help the problem.
    - prophesi 9y ago
      Yep, precisely! And if I'm having peer discovery issues with just two nodes, I can't imagine what you guys are having to go through. :/ For the curious: you'd run `ipfs id` on the nodes to get their addresses. Then you'd run `ipfs config edit` on them and add the other node's address to the bootstrap section. https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#bootstrap https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#b... But yeah... They'd still mysteriously not connect to each other at times.
      - StavrosK 9y ago
        Yep :( It's pretty disheartening to work on a product for some time and have the underlying technology just not work up to your standard. Hearth is basically hit and miss for that reason, sometimes files show up right away and it's amazing, sometimes they time out and it's useless. Very frustrating, and there's absolutely nothing we can do about it.
        pookeh 9y ago
        I haven't looked at IPFS in depth but could this be because both the nodes are behind a nat and they need a relay node?
        StavrosK 9y ago
        No, at least one wasn't. Plus, this happened even when they were directly connected.