Maybe Profiling vault performance could be a good start. It’s not exactly a comparison to traditional client-server.
The chunks are assembled by the client, so the network only needs to know how to deliver chunks. This allows for very simple caching rules that should give high performance, especially for popular chunks.
What happens if this is chosen deliberately by the client app to be the same as an existing xor name on the network?
Or slightly extending that idea, what if a user computes the xor name for an immutable data chunk before uploading to the network, creates an MD at that same xor name, then tries to upload the immutable data? Won’t this cause conflicts? I’m just not quite clear on how names can be set by someone other than the network but still be secure.
Thanks for clarifying about MD. I really appreciate your in-depth knowledge of the code.