The default (ConnMgr.LowWater=600 and HighWater=900) are bit too high for desktop use. Those are aimed at server use.
Desktop users may experience issues if they are connected to a LAN managed by inexpensive consumer routers (some models crash when 1k of connections is passed).
IPFS Desktop has been running for years with (LowWater=50 and HighWater=300)
and I suggest Brave sets the same values after ipfs init as it decreases the risk of crashing LAN for users.
Using a clean profile, visited ipfs://QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR to trigger IPFS infobar.
Installed IPFS from infobar.
Opened ~/Library/Application Support/BraveSoftware/Brave-Browser/brave_ipfs/config file.
Confirmed updated config values of LowWater=50 and HighWater=300.
Spot checked able to load ipfs:// and ipns:// URLs without issue.
Verification passed on
Brave | 1.19.84 Chromium: 88.0.4324.87 (Official Build) (64-bit)
-- | --
Revision | dd01ff8f58c65af81127ad5c105c79d5b571d8f3-refs/branch-heads/4324@{#1702}
OS | Windows 10 OS Version 2004 (Build 19041.685)
Using a clean profile, visited ipfs://QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR to trigger IPFS infobar.
Installed IPFS from infobar.
Opened ...AppData\Local\BraveSoftware\Brave-Browser\User Data\brave_ipfs/config file.
Confirmed updated config values of LowWater=50 and HighWater=300.
lidel commentedJan 12, 2021
The default (
ConnMgr.LowWater=600andHighWater=900) are bit too high for desktop use. Those are aimed at server use.Desktop users may experience issues if they are connected to a LAN managed by inexpensive consumer routers (some models crash when 1k of connections is passed).
IPFS Desktop has been running for years with (
LowWater=50andHighWater=300)and I suggest Brave sets the same values after
ipfs initas it decreases the risk of crashing LAN for users.cc @bbondy @yrliou
The text was updated successfully, but these errors were encountered: