Closed michaelavila closed 5 years ago
@michaelavila where's the current best place to go to read up on existing providing strategies and related docs in ipfs?
This thread on content routing and providing seems relevant: https://github.com/ipfs/notes/issues/162, linked from https://github.com/ipfs/notes/issues/212
@andrew yes.
FWIW: There are really two provider systems generally being discussed, (1) the providing system in libp2p and (2) the providing system in ipfs. I've been focused on the ipfs specific providing system, which up to this point has really just been bitswap aggressively providing every block it comes into contact with. Some of what's in these links is libp2p specific and some is useful for ipfs.
Edit: Clarification: The ipfs providing system is just an abstraction that uses the libp2p providing system.
@michaelavila do you know of any existing benchmarks or performance tests that have been set up around providing? Like do we know what the current max size of a directory we can provide on the DHT today?
@andrew no, not that I know of.
@michaelavila is presenting on Friday (recorded call) for the latest on this and related work.
@michaelavila are there other pieces of documentation on our latest understanding of workable and non-workable solutions to improve providing in go-ipfs that should be indexed here?
@momack2 my apologies, I didn't see your message. I'm compiling this information into an issue that's not online yet. I'll circle back once it's online. To be honest, I don't have a lot of strategy specific information regarding package managers as we didn't spend too much time talking about it. I opened this ticket to start that, but my priorities were shifted a little.
And this is done! https://github.com/ipfs/package-managers/issues/84 . Also, there's a recording. We should find it and drop it here.
Recording: https://youtu.be/eSTEc4QFpc4
Since we can't provide all of the blocks, which should we provide?