Analysis for Logos Storage vs. Deluge Benchmarks - Static Network Dissemination Experiment

1 Introduction

This document contains the analysis for the Deluge vs. Logos Storage benchmarks. All data is obtained from our benchmark suite. Each node runs in its own virtual machine. The exact configuration for the machines has varied over time, but those are typically \(4\)vCPU, \(8\) or \(16\)GB machines running either on Hetzner or Digital Ocean.

The benchmark consists in running a series of static dissemination experiments, where a file of size \(b\) is disseminated across a swarm (set of nodes) of size \(n\). Each swarm is split into a seeder set of size \(s\) and a leecher (or downloader) set of size \(l = n - s\). Seeders have the complete file at the start of the experiment, whereas leechers have nothing. The experiment consists in starting the leechers and then measuring the time it takes for each to download the file.

Leechers are started as closely as possible to each other so that they start downloading the file roughly at the same time. This stresses the network and, under these conditions, should provide us with a reasonable idea of what the lower bound on performance should be.

For a given network configuration \((n, s, l = n - s)\), we define it’s seeder ratio as \(r = s / n\). A higher seeder ratio should lead to faster dissemination, but if the swarms are homogeneous and scalable, the impact should not be large. We also expect close-to-constant performance for a given seeder ratio after for large enough swarms. Deviations from such behavior are likely issues.

We are then interested in asserting how system performance degrades under increasing file or swarm sizes. We expect larger files to take roughly linearly longer to download. We expect system performance to increase with swarm size up to a maximum. Deviations from this behavior likely reflect issues with the protocol.

Each experiment is ran \(10\) times. We rotate seeders and leechers at random at every \(5\) repetitions (so twice in total). This should allow us to account for performance differences that might arise from lack of overlay homogeneity or other factors.

2 Results

2.1 Benchmark Data - Raw

Raw data in tabular format:

2.2 Median Download Speed

Figure 2.1: Median download speed for Deluge and Logos Storage

2.3 Median Download Time

Figure 2.2: Median time to download a whole file for Deluge and Logos Storage

2.4 Median Time to First Byte

The time elapsed from the moment in which we ask a node to download a file to the time in which it logs having downloaded the first \(x\%\) of the file – whatever the logging granularity is – marks our time to first byte. This is actually a pessimistic approximation as it factors in i) DHT lookup latency; ii) swarm bootstrap latency; iii) a fraction, typically \(1/100^{th}\), of the download time. This should impact smaller files more than it impacts larger files.

Figure 2.3: Median time-to-first-byte for Deluge and Logos Storage

2.5 Median Transfer Speed

“Transfer” speed is download speed calculated excluding the time-to-first-byte. Since the time-to-first-byte approximation is pessimistic, the transfer speed is optimistic. It is still useful as a proxy for actual relative transfer speed, however, particularly for larger files.

2.6 Median Download Time Ratio

Let \(t_d\) and \(t_c\) be the median times that Deluge and Logos Storage, respectively, take to download some file of a given size. The median download time ratio is defined as \(m = t_c / t_d\). When \(m < 1\), Logos Storage is faster than Deluge. It is otherwise \(m\) times slower to download the same file.

Figure 2.4: Median download time ratio for Logos Storage and Deluge