What happens when you upload
- Your browser sends the file to our upload server in chunks.
- The server encrypts it with a fresh key, cuts it into slabs and erasure-codes every slab into shards, then stores each shard on a different node, paid with vouchers from the demo’s own wallet.
- You get a link with the file’s address and its key. The gateway at files.slab.me.uk fetches enough shards for each part you read, checks and decodes them, and streams the result to your browser. A website’s pages, styles and images are each fetched this way.
What the numbers mean
- First frame: time from pressing play until the video plays. It includes finding the shard holders, fetching the file’s manifest and decoding the first slabs.
- Stalls: how often playback stopped to wait for data, and for how long in total.
- Seek: jump to the middle and time how long until it plays again. Only the slabs around that point are fetched (an HTTP range read).
- Website: time until this website has finished loading in its frame.
How to read the result
- Location matters. All of the testnet’s nodes and the gateway are in one data centre in Germany, so readers near it see faster loads than readers far away.
- Caches. Every request carries a random
?nocache=value, so neither your browser nor the CDN in front of the gateway can answer it from a stored response: each byte comes from the storage nodes. A file read often may still be in the nodes’ memory, so the first viewer of the day waits longest. - The testnet can be reset, and uploads are paid for 30 days. Don’t store anything you can’t lose.
Big Buck Bunny © Blender Foundation, peach.blender.org, licensed under CC BY 3.0. Re-encoded at 1080p, 2.2 Mbit/s, and a 3:30 clip at 2160p60, 39 Mbit/s.