4 ms·
In what way is ipfs a monster? It is a single go binary that does a tiny number of jobs.
by jstanley 3y ago
In what way is ipfs a monster? It is a single go binary that does a tiny number of jobs.
- Grimburger 3y agoClient side compute for other random people is probably what GP is talking about here.
- jstanley 3y agoIPFS doesn't do that, are you thinking of something else?
- Grimburger 3y agohttps://discuss.ipfs.tech/t/high-bandwidth-and-cpu-usage-from-go-ipfs/13982 https://discuss.ipfs.tech/t/high-bandwidth-and-cpu-usage-fro...
- kkfx 3y agoDid you try to look at IPFS codebase size?
- jstanley 3y ago~/kubo$ find . -name \*.go | xargs wc -l | tail -1 59629 total Doesn't seem that big?
- kkfx 3y agoYES! Compared to a simple IRC server+client or XMPP definitively.
- jstanley 3y agoWell irssi is an IRC client and is bigger than that: ~/irssi$ find . -name \*.[ch] | xargs wc -l | tail -1 88551 total https://github.com/irssi/irssi https://github.com/irssi/irssi Obviously ipfs doesn't have the chat UI, ipfs is just a protocol layer. But it is a more complicated protocol than IRC, so you'd expect it to be larger. I don't think it's large out of proportion, certainly not large enough to call it a "MONSTER software".
- bogwog 3y agoMy users complain all the time about the LoC of my codebase
- mrusme 3y agoI'd like to point out that you probably cloned https://github.com/ipfs/kubo https://github.com/ipfs/kubo there, which is only one part of what accounts for the "IPFS codebase". If you want to find out the actual LoC, I'm afraid you will need to dig through https://github.com/ipfs/kubo/blob/master/go.mod https://github.com/ipfs/kubo/blob/master/go.mod and pick everything that's github.com/ipfs/*, github.com/libp2p/* and github.com/ipld/*.
- jstanley 3y agoFair point!
- jeroenhd 3y agoIPFS is a resource hog. Not sure if it's just the implementation or if it's because of architectural limitations, but it gobbles up CPU and RAM much more than you'd expect it to. I shut down my self-hosted IPFS server because it kept pegging a CPU core doing what seemed like nothing (no new pins, barely any network traffic, just sitting there).
- holmesworcester 3y ago(Quiet founder here) Yes, IPFS is a resource hog when running on the global IPFS network, but Quiet never touches that network, and this improves performance a lot. I can run Quiet in the background all day on my Pixel 6 and we haven't even started optimizing for battery life yet.