Skip to content

Your file is not a single thread. Briskfetch weaves it with many shuttles, all at once.

When a server caps each connection, Briskfetch splits the file into parts, requests them at the same time over separate connections and writes each one to its own place in the file. Not released yet. We are collecting applications from testers and organisations.

No fee, no commitment. You can have your application deleted at any time.

Finished kilim pattern with Briskfetch woven in dot letters in the middle.

Simulation: a trace of the real planner (dl-plan), simulated network, time compressed. Your pointer or finger is the light; drag across the fabric to unpick stitches.

Pull the guide thread: rows unravel and are woven again
About the name

Brisk: nimble, quick. Fetch: to go and bring back. Briskfetch splits a file into parts and fetches the parts at the same time.

Why does a file arrive slowly when your line is idle?

The problem

Many servers cap the speed of a single connection. Even if your line could carry much more, the file arrives at that one connection's speed, in order from start to end.

What Briskfetch does

It splits the file into parts and requests them at the same time over separate connections. Each part is written to its own position in the file; there is no merge step afterwards.

A download, like a kilim

Each stitch of the fabric below stands for a byte of the file. As you scroll, two downloads of the same 64 MiB file play: first a single connection, then the Briskfetch planner.

Single connection · Simulation clock 0.0 s Scenario: 10 Mbit/s per connection, 100 Mbit/s line. A simulation, not a measurement.
  1. One thread

    An ordinary download requests the file over one connection, in order from start to end. When the server caps each connection, the file moves at that cap; the rest of your line sits idle.

  2. New shuttles

    Briskfetch starts with one connection and opens more while the line allows. Each connection asks for a different part of the file. Every colour in the fabric is a separate connection.

  3. Every part in its place

    Each part that arrives is written to its own position in the file. Long remaining sections are split and handed to new connections; no part waits for the one before it.

  4. No merge step

    When the last shuttle stops, the file is ready. There are no separate part files and no merging afterwards. In this scenario the single connection had reached only part of the file by then.

When does it help, and when doesn't it?

Briskfetch does not speed up every download. The gain depends on where the bottleneck is.

  • The server caps each connection

    It helps. Several connections use the idle part of your line.

  • Your line is already full

    It doesn't help. Nothing goes beyond the capacity of your line. In the simulation both downloads finish in almost the same time.

  • The server doesn't support range requests

    It downloads over one connection. A server that won't serve the file in parts leaves nothing to split.

  • The site uses HTTPS

    Partly. HTTPS downloading is written in the download engine and was tested in the lab against a local server. Certificates are not yet read from the operating system's certificate store, and phone and Windows support is not finished. There is no speed measurement on the real internet.

Lab measurement:
6.81

In the lab, the time of a single connection divided by the time of Briskfetch (median of 5 runs). No measurement on the real internet yet; no confidence interval computed.

Server
Local test server, plain HTTP
Per-connection cap
10 Mbit/s
Total cap
100 Mbit/s
Latency
20 ms
File
64 MiB
Fixed 8 connections
7.95 (same conditions)
When the line is the limit
1.0011 (15 Mbit/s total, 32 MiB, 7 pairs): practically no difference
Date

Try it yourself

Pick the server's cap and your line speed. The two strips are two simulated downloads of the same file; both play at the same speed, so you can see which finishes first.

Single connectionnot finished yet
Briskfetch plannernot finished yet

Traces load when you reach this section.

A simulation, not a measurement: a deterministic network model with a per-connection cap, a shared line, slow start and connection setup delay, driven by the real dl-plan planner. Real speed depends on your network and the server. File 64 MiB, round trip 40 ms.

The Briskfetch principle

No merge step. Every part is woven into its own place in the fabric; when the last weft is thrown, your file is ready.

Where does it stand today?

There is no download button because there is no released version. We state plainly what is ready.

Exists

  • The dl-plan planner
  • The simulation and traces on this page
  • Lab measurement tools
  • App interface skeleton

In progress

  • The dl-engine download engine
  • HTTPS support: written in the engine, tested in the lab; system certificate store, phone and Windows support not finished

Not yet

  • A released version
  • Gain measured on the real internet
  • Browser integration
  • A paid version
Platforms
PlatformStatus
Windows, macOS, LinuxIn development
AndroidInterface skeleton with sample data
iOSNo system-wide acceleration; iOS does not allow it
BrowserDemo with sample data only

Questions

What is Briskfetch?

A download manager. When a server limits the speed of each connection, it splits the file into parts, requests them at the same time over separate connections and writes each part to its own place in the file.

Can I download it now?

No. There is no released version. We will write to applicants when early access opens.

Does it speed up every download?

No. It helps when the server caps each connection. If your line is already full, or the server doesn't support range requests, there is no gain. Details in the "When does it help" section.

Does it work on HTTPS sites?

Partly. HTTPS downloading is written in the engine and was tested in the lab against a local server. Certificates are not yet read from the operating system's certificate store, HTTPS on phones and Windows is not finished, and there is no speed measurement on the real internet. Some servers' partial-response format (a 206 response sent with chunked transfer) is also rejected today. There is no released version.

Where do the numbers on this page come from?

There are two sources. The fabric animations are traces the real planner produced on a simulated network. The single measurement (6.81) comes from a local lab server and is shown with its conditions. There is no measurement on the real internet yet.

What does "no merge step" mean?

Some downloaders write parts to separate files and merge them when the download ends. Briskfetch writes each part straight to its position in the final file, so there is no merge step waiting at the end.

Which platforms will it support?

Windows, macOS and Linux versions are in development. There is an interface skeleton for Android. iOS does not allow system-wide download acceleration, so we won't offer such a feature there.

What happens if I become a tester?

We write to you when early access opens. No fee, no commitment. Just use the test version and tell us what it helps with and what it doesn't.

What does the organisation service mean?

There is no ready package or price for organisations yet. If you have a need such as large file distribution, write to us and we will look at it together.

How do I get my application deleted?

Fill in the same form with the same email address and write "deletion request" and your application code in the message field. Requests are handled by hand. Details in the privacy notice.

Apply for early access

One form, two paths: users who want to test and organisations. We use only the information in this form, to review your application and to write to you.

The holes above the form show the required fields you have filled in, like the punched cards of old looms. When you send it, the card goes into the loom.

What are you applying for?

What kind of files, from which servers, how often. Up to 1000 characters.