BAD SKY.NET

YABS to JSON Converter

Convert raw YABS benchmark output into clean JSON for scripts, dashboards, VPS comparisons, and internal tooling.

What is the YABS to JSON converter?

YABS, short for Yet Another Bench Script, generates benchmark reports for VPS and dedicated servers as plain-text terminal output. That format is easy to read in SSH sessions, but it is inconvenient when you want to store benchmark data, compare servers programmatically, or ship results into another system.

This YABS to JSON converter parses raw benchmark text and turns it into a structured payload that is easier to validate, save, search, and reuse. If you benchmark infrastructure regularly, JSON gives you a stable format for reporting CPU, disk, network, and Geekbench results without writing your own parser for each run.

Want to inspect the format before pasting your own output? Open a real YABS example .

Why convert YABS output to JSON?

Raw YABS output is fragile. Small changes in spacing, headers, or line wrapping can break shell scripts and regular expressions. A structured JSON payload is easier to parse safely and gives you predictable keys for downstream tools.

Teams use converted YABS JSON to archive benchmark history, compare VPS providers over time, trigger alerts on regressions, and import standardized metrics into APIs or databases. YABS itself is open source, and you can inspect the upstream project in the official YABS repository.

Automate benchmark reporting

Push structured results into dashboards, CI jobs, spreadsheets, or object storage without maintaining brittle parsing logic.

Standardize VPS comparisons

Keep every benchmark run in the same machine-readable format so provider-to-provider comparisons stay clean and repeatable.

How to use this YABS converter

1.
Paste the full raw benchmark output
Include the full YABS response, not just a partial section, so the parser can capture system info, disk tests, network tests, and benchmark scores.
2.
Convert and review the JSON
Run the conversion, then quickly scan the generated keys and values to confirm the important measurements were parsed correctly.
3.
Copy the result into your workflow
Use the JSON in scripts, internal apps, benchmark archives, or API payloads wherever you need consistent machine-readable YABS data.
Example
Full YABS raw output example

Open by default so you can immediately compare your own benchmark output against a known-good sample.

Click to collapse

YABS example response

Use this sample to test the converter or to compare your own benchmark output against the expected raw format.

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2023-04-23                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Sun 23 Apr 2023 01:41:14 PM EDT

Basic System Information:
---------------------------------
Uptime     : 342 days, 18 hours, 35 minutes
Processor  : Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz
CPU cores  : 12 @ 4693.667 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 15.5 GiB
Swap       : 14.9 GiB
Disk       : 864.5 GiB
Distro     : Ubuntu 20.04.6 LTS
Kernel     : 5.4.0-110-generic
VM Type    : NONE
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : Clouvider Limited
ASN        : AS62240 Clouvider
Host       : USA Network
Location   : New York, New York (NY)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 405.41 MB/s (101.3k) | 407.96 MB/s   (6.3k)
Write      | 406.48 MB/s (101.6k) | 410.11 MB/s   (6.4k)
Total      | 811.90 MB/s (202.9k) | 818.08 MB/s  (12.7k)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 380.21 MB/s    (742) | 394.55 MB/s    (385)
Write      | 400.41 MB/s    (782) | 420.82 MB/s    (410)
Total      | 780.62 MB/s   (1.5k) | 815.37 MB/s    (795)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping
-----           | -----                     | ----            | ----            | ----
Clouvider       | London, UK (10G)          | 1.61 Gbits/sec  | 2.39 Gbits/sec  | 77.5 ms
Scaleway        | Paris, FR (10G)          | busy            | 2.25 Gbits/sec  | 83.3 ms
Clouvider       | NYC, NY, US (10G)         | 9.10 Gbits/sec  | 8.85 Gbits/sec  | 1.21 ms

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping
-----           | -----                     | ----            | ----            | ----
Clouvider       | London, UK (10G)          | 2.00 Gbits/sec  | 21.1 Mbits/sec  | 76.7 ms
Scaleway        | Paris, FR (10G)          | 2.66 Gbits/sec  | 1.56 Gbits/sec  | 75.9 ms
Clouvider       | NYC, NY, US (10G)         | 3.42 Gbits/sec  | 7.80 Gbits/sec  | 1.15 ms

Geekbench 4 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 5949
Multi Core      | 23425
Full Test       | https://browser.geekbench.com/v4/cpu/16746501

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 1317
Multi Core      | 5529
Full Test       | https://browser.geekbench.com/v5/cpu/21102444

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 1549
Multi Core      | 5278
Full Test       | https://browser.geekbench.com/v6/cpu/1021916

YABS completed in 12 min 49 sec

When raw YABS to JSON is useful

Provider benchmarking

Track and compare benchmark runs from multiple VPS vendors in a format that is easy to sort and analyze.

Internal automation

Feed benchmark data into jobs, alerts, or reporting systems that expect structured values instead of plain text blocks.

Historical archives

Store normalized benchmark records over time so you can spot regressions, hardware changes, or noisy test runs later.

FAQ

Does this tool run in the browser?

The page sends your pasted YABS text to the site endpoint that performs the raw-to-JSON conversion and returns the parsed payload.

Should I keep the original YABS text too?

Yes. Keep the raw benchmark output so you can audit the original result or re-run conversion later if your downstream schema changes.

Can I use the example output for testing?

Yes. The default-open example block is there specifically so you can inspect the format and copy a realistic sample benchmark response immediately.