[gomobile-lib] better control over the max number of connected peers

aeddi commented 4 years ago

For the moment, the limits that we set in the config concerning the number of peers (high/low watermarks, grace period) does not seem to regulate correctly the maximum number of connected peers (probably due to a misuse / misunderstanding on our part).

We need to find a way to precisely control the maximum number of peers a device is connected to because:

On iOS and Android, the number of connected peers is strongly related to the resource consumption
On iOS a problem occurs very quickly: the OS throws "too many open files" errors when it reaches about 200 connected peers (this limit is not configurable on iOS)

I will do precise tests with different high/low watermarks and grace period settings and post reports on this issue so that we have a better view of the problem before thinking about solutions.

jefft0 commented 1 year ago

Hi @aeddi . If we upgrade kubo to get the Resource Manager (like we did in weshnet), do you think it would resolve this issue?

aeddi commented 1 year ago

Hi :) Honestly I haven't tested the new Kubo Resource Manager yet, it could resolve the issue, would be worth a try

ipfs-shipyard / gomobile-ipfs

[gomobile-lib] better control over the max number of connected peers #20