id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
3766	Protocol is potentially high-latency and high bandwidth overhead for small files	itamarst	exarkun	"Imagine uploading a new, small file. As I understand it, this will require:

1. Create a storage index.
2. Upload each of the shares, e.g. 10 HTTP queries if there's 10 shares. 

One can't do _all_ queries in parallel, only uploads, because of the race condition between the uploads and the storage index existing. So even a clever, async client implementation will still require two HTTP roundtrips for each upload.

In addition to double latency (or 11× latency for a naive client, which maybe we don't care about), there's also a bunch of HTTP protocol overhead for uploading a file.

One can imagine an optimized variant of the API that includes both storage index and share creation in a single HTTP API call, for smaller files. This is, however, an optimization, and probably needn't exist in the first version."	enhancement	new	normal	HTTP Storage Protocol v2	unknown	n/a