ntruprime-speed(1)

📦
version 0~20241021 · 3 versions
, in debian trixie, ubuntu questing

✨ ntruprime-speed — the manual, but make it cute ✨

okay bestie, welcome to ntruprime-speed(1), the lil page that tells you how to run some libntruprime speed tests 💖 buckle up, it's giving benchmarking but make it fashion.

🌸 NAME 🌸

ntruprime-speed — run some libntruprime speed tests, bestie 🏃♀️💨

🎀 SYNOPSIS 🎀

ntruprime-speed

like… that's it. no flags, no args, no drama. you just run it. slay 💅

🦋 DESCRIPTION 🦋

okay so ntruprime-speed runs some tests of the speed of the libntruprime implementation of the Streamlined NTRU Prime cryptosystem. that's the whole vibe. it just goes and measures things. 🔥

real talk though: the ntruprime-speed output format is subject to change. subject to change!! so don't you dare parse it and build a whole pipeline on it, okay? it will absolutely ghost you.

here's what the output lines look like rn, with the current format, from a ntruprime-speed run on an Intel Skylake CPU core 👇

kem_sntrup761 selected implementation factored compiler clang -Wall -fPIC -fwrapv -Qunused-arguments -O2; Ubuntu clang version 14.0.0-1ubuntu1.1; Target: x86_64-pc-linux-gnu; Thread model: posix; InstalledDir: /usr/bin
kem_sntrup761_keypair selected 1158 779846 +112137+5141+1312+565-207-153+66-18+35+1650-109+4-144+414-119-69-243+66+82-110-1-16+174+864+741-52-1+57-180-538-312-116
kem_sntrup761_enc selected 1039 40275 +8153+1104+323-39+36-1-107-27-99-17-15-65+74-33-102-24-30+69+99-106+7+33+59-5+175-60-29+152+21-82+90-78
kem_sntrup761_dec selected 32 52834 +36240+2014+438+165+96+109+62-8-78+20+67-30-112-59+27-25-3+31+15-118+102-64-84+19-121+57-35+120-125-147-80-75

so what are these lines even saying? let me translate 🧚

  • the automatically selected implementation for the sntrup761 parameter set was the factored implementation, compiled with the clang options shown up there 👀
  • it took an interquartile mean (IQM) of 779846 CPU cycles to generate a key pair
  • an IQM of 40275 CPU cycles to encapsulate a session key
  • and an IQM of 52834 CPU cycles to decapsulate a session key

and the numbers like 52834 +36240+2014+...? those are the timings for a series of consecutive operations, periodt:

  • the IQM was 52834 cycles
  • the first run took 36240 cycles more than the IQM
  • the second run took 2014 cycles more than the IQM
  • etc etc, you get it 🌈

now the numbers sitting immediately after selected on the keypair, enc, and dec lines? those say that:

  • a public key has 1158 bytes
  • a ciphertext has 1039 bytes
  • and a session key has 3 bytes

(three. THREE. iconic honestly.)

💜 SEE ALSO 💜

and that's the whole page, no cap 💖 this little ntruprime-speed(1) manual page is yours truly, and it's signing off from the ntruprime-speed(1) corner of the manual set 🫶 go forth and benchmark, bestie ✨🎀

📦 where this page comes from