askiiart/engl-2311-blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

FINALLY add the rest of the graphs with this hellish code

Browse source 
i will be repenting to the DRY gods for the rest of eternity
This commit is contained in:
askiiart 2024-11-17 23:40:06 -06:00
parent 92ce85cf59
commit 4e20db145e
Signed by untrusted user who does not match committer: askiiart
GPG key ID: EA85979611654C30
8 changed files with 663 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

19
blog/benchmarking-dwarfs.html
View file

@ -93,13 +93,25 @@
script</a> to make it a bit easier, I put the resulting graphs
in here ↓</p>
<h3 id="sequential-read">Sequential read</h3>
<div>
<canvas id="seq_read_chart" class="chart">
</canvas>
</div>
<h3 id="random-read">Random read</h3>
<div>
<canvas id="rand_read_chart" class="chart">
</canvas>
</div>
<h3 id="sequential-read-latency">Sequential read latency</h3>
<div>
<canvas id="seq_read_latency_chart" class="chart">
</canvas>
</div>
<h3 id="random-read-latency">Random read latency</h3>
<div>
<canvas id="rand_read_latency_chart" class="chart">
</canvas>
</div>
<p>The FUSE-based filesystems run into a bit of trouble here -
with incompressible data, DwarFS has a hard time keeping up for
some reason, despite keeping up just fine with larger random
@ -127,7 +139,11 @@
<h2 id="footnotes">Footnotes</h2>
<!-- JavaScript for graphs goes hereeeeeee -->
<script src="https://cdn.jsdelivr.net/npm/chart.js"></script>
<script src="/assets/benchmarking-dwarfs/js/declare_vars.js"></script>
<script src="/assets/benchmarking-dwarfs/js/seq_read.js"></script>
<script src="/assets/benchmarking-dwarfs/js/rand_read.js"></script>
<script src="/assets/benchmarking-dwarfs/js/seq_latency.js"></script>
<script src="/assets/benchmarking-dwarfs/js/rand_latency.js"></script>
<section id="footnotes"
class="footnotes footnotes-end-of-document" role="doc-endnotes">
<hr />
@ -144,8 +160,7 @@
generates regular polygons and writes their data to a file. I
chose this because it was an artificial and reproducible yet
fairly compressible dataset (without being extremely
compressible like null data).<br />
compressible like null data).
<details open>
<summary>
3-sided regular polygon data

19
blog/benchmarking-dwarfs.md
View file

@ -59,8 +59,18 @@ After processing [the data](/assets/benchmarking-dwarfs/data/) with [this script
### Sequential read
<div>
<canvas id="seq_read_chart" class="chart"></canvas>
</div>
### Random read
<div>
<canvas id="rand_read_chart" class="chart"></canvas>
</div>
### Sequential read latency
<div>
@ -69,6 +79,11 @@ After processing [the data](/assets/benchmarking-dwarfs/data/) with [this script
### Random read latency
<div>
<canvas id="rand_read_latency_chart" class="chart"></canvas>
</div>
The FUSE-based filesystems run into a bit of trouble here - with incompressible data, DwarFS has a hard time keeping up for some reason, despite keeping up just fine with larger random reads on the same data, and so it takes 3 to 4 seconds to run random read latency testing on the 25 GiB random file. Meanwhile, when testing random read latency in `fuse-archive` pretty much just dies, becoming ridiculously slow (even compared to DwarFS), so I didn't test its random read latency at all and just had its results put as 0 milliseconds.
### Summary and notes
@ -98,4 +113,8 @@ The FUSE-based filesystems run into a bit of trouble here - with incompressible
<!-- JavaScript for graphs goes hereeeeeee -->
<script src="https://cdn.jsdelivr.net/npm/chart.js"></script>
<script src="/assets/benchmarking-dwarfs/js/declare_vars.js"></script>
<script src="/assets/benchmarking-dwarfs/js/seq_read.js"></script>
<script src="/assets/benchmarking-dwarfs/js/rand_read.js"></script>
<script src="/assets/benchmarking-dwarfs/js/seq_latency.js"></script>
<script src="/assets/benchmarking-dwarfs/js/rand_latency.js"></script>