Score:0

Seeking Advice re. IPFS Clustering - Overhead, Performance, Design Guidance

de flag

I’m about to rebuild a server cluster - currently set up for high reliability & availability - RAID, disk mirroring, automatic failover, all that good stuff.

I’ve been thinking about replacing the storage “plumbing” with a distributed filesystem - that extends beyond the cluster to another location, and to various laptops & desktops - one big file system for an organization & its community.

From 50,000 feet, just turning all the machines into one big IPFS cluster would seem to make sense - but one wonders about all the processing & data transfer overhead. Also, the latency - how fast will systems sync if they’re on neighboring machines. And then there's the matter of checkpointing & reliable failover.

Can anybody point at some analysis of the processing & network overhead associated with IPFS & IPFS-cluster? Any experience and/or suggestions for using IPFS as a generic, distributed, high-availability storage network? Case studies? Places to start looking? (Note: Didn't get a single response on discuss.ipfs.tech - doesn't seem to be very active as a support community.)

Thanks Very Much,

Miles Fidelman

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.