3 ms·
Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working
by 1vuio0pswjnm7 5y ago
Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working on.
- whyrusleeping 5y agoPeople are working on smaller unixy tools to do fewer things well, but at least for the main codebase we are limited by go itself. Making binaries smaller is not simple at all... You might be interested in checking out the rust implementation: https://github.com/rs-ipfs/rust-ipfs https://github.com/rs-ipfs/rust-ipfs Im not actually sure how well it would work for what youre after, but it is an option!
- 1vuio0pswjnm7 5y agoI was thinking more along the lines of splitting up the whopping 56MB single binary into smaller, individual programs. There is a version of libp2p, which is the library used by IPFS, that is written in C++. Perhaps that is another option.
- 1vuio0pswjnm7 5y agoAnother option: https://github.com/ipfs-rust/ipfs-embed/ https://github.com/ipfs-rust/ipfs-embed/
- cyanydeez 5y agowhat platforms are you targetting that cant take 24mb?
- 1vuio0pswjnm7 5y agoEmbedded systems, small form factor computers that have limited resources, older computers. 24MB is just the total for the compressed packages. The ipfs binary is actually over twice that size.
- saurik 5y agoI mean, if you are on a sufficiently-embedded system that you don't have 24MB of disk space, you almost certainly don't have enough RAM or CPU to run IPFS anyway.
- 1vuio0pswjnm7 5y ago"if" (Your guess may be incorrect) In some cases I have 24MB but I want to conserve space for other programs. The go-ipfs uncompressed binary is 56MB not 24MB. That is a multiple times larger than the combined size of the kernel and userland I use. Seems like making ipfs run on smaller systems is a goal some are interested in pursuing. I could be wrong but I doubt I am the the only one interested in this. https://github.com/Twodragon0/OpenWRT-IPFS https://github.com/Twodragon0/OpenWRT-IPFS
- saurik 5y agoFWIW, most Raspberry Pi based systems are not what I would want to call "embedded"; and, in the grand scheme of things, they actually have fairly large CPUs. I am surrounded by such devices, and they all have plenty of storage as SD cards don't even come in tiny sizes anymore... I imagine we are simply at a point in time where the cost of creating an individual object encased in a plastic shell has high enough intrinsic overhead that having less than a gigabyte of storage would be nonsensical.
- 1vuio0pswjnm7 5y agoFWIW, OpenWRT is used for more than just RPi. Also, I never said "embedded" was the only use case. The categories were 1. embedded 2. small form factor computers with limited resources 3. older computers. That is a quick list, not a fully inclusive one. To be truthtful, I am not comfortable with 56MB binaries even on newer laptops where I have GB of free space. I simply cannot agree with any comments that imply that keeping size small is a worthless goal. I could list hundreds of past and current examples where people are trying to reduce size and/or complaining about large size. k/shakti fits in a 2000's-era CPU cache. Arguably it does more than go-ipfs. At least, one can certainly do more with it. It makes no sense to argue against making programs small, for a variety of reasons I am not even bothering to mention. Large programs offer no additonal benefits. Generally, no one is forcing anyone else to use smaller, faster programs if they do not want to, UNIX utilities being one obvious exception; there are others. I will continue to write, use and appreciate smaller, faster, more resource-efficient programs. I am not the only one. You will have many more folks than just me to convince that they should ignore size.
- mtnGoat 5y agois 24mb really considered big these days? ive been to home pages that are heavier than that.
- 1vuio0pswjnm7 5y agoDecompressed binary is 56MB not 24. I use a text-only browser. It does not automatically source resources external to the page. I do not experience "heavy" pages. What you refer to is probably what happens when pages try to source a gazillion different resources.