I would like to know how to calculate the encryption time for AES-CCM.
The Crypto++ wiki provides an article Benchmarks. It provides a lot of details regarding library performance, how throughput is calculated, and it even references the source code where the actual throughput is measured. Believe it or not, a simple call to clock
works just fine to measure bulk encryption. Also see Benchmarks | Timing Loop in the same wiki article.
To benchmark AES/CCM, do something like the following. It is based on the Crypto++ benchmarking code, but it uses a ThreadUserTimer
instead of a direct call to clock
. ThreadUserTimer
works across all OSes and all versions of C++.
You need to dial-in your processor speed at cpuFreq
. You should also run ./governor.sh perf
to move the CPU from an idle or C-level sleep state, but you can't because it is a Linux script. You can find it in the TestScript/
folder.
#include "cryptlib.h"
#include "secblock.h"
#include "hrtimer.h"
#include "osrng.h"
#include "modes.h"
#include "aes.h"
#include "ccm.h"
#include <iostream>
const double runTimeInSeconds = 3.0;
const double cpuFreq = 2.7*1000*1000*1000;
int main(int argc, char* argv[])
{
using namespace CryptoPP;
AutoSeededRandomPool prng;
SecByteBlock key(16);
prng.GenerateBlock(key, key.size());
CCM<AES>::Encryption cipher;
cipher.SetKeyWithIV(key, key.size(), key);
const int BUF_SIZE=RoundUpToMultipleOf(2048U,
dynamic_cast<StreamTransformation&>(cipher).OptimalBlockSize());
AlignedSecByteBlock buf(BUF_SIZE);
prng.GenerateBlock(buf, BUF_SIZE);
double elapsedTimeInSeconds;
unsigned long i=0, blocks=1;
ThreadUserTimer timer;
timer.StartTimer();
do
{
blocks *= 2;
for (; i<blocks; i++)
cipher.ProcessString(buf, BUF_SIZE);
elapsedTimeInSeconds = timer.ElapsedTimeAsDouble();
}
while (elapsedTimeInSeconds < runTimeInSeconds);
const double bytes = static_cast<double>(BUF_SIZE) * blocks;
const double ghz = cpuFreq / 1000 / 1000 / 1000;
const double mbs = bytes / 1024 / 1024 / elapsedTimeInSeconds;
const double cpb = elapsedTimeInSeconds * cpuFreq / bytes;
std::cout << cipher.AlgorithmName() << " benchmarks..." << std::endl;
std::cout << " " << ghz << " GHz cpu frequency" << std::endl;
std::cout << " " << cpb << " cycles per byte (cpb)" << std::endl;
std::cout << " " << mbs << " MiB per second (MiB)" << std::endl;
// std::cout << " " << elapsedTimeInSeconds << " seconds passed" << std::endl;
// std::cout << " " << (word64) bytes << " bytes processed" << std::endl;
return 0;
}
Running it on a Core i5-6400 at 2.7 GHz results in:
$ g++ bench.cxx ./libcryptopp.a -o bench.exe
$ ./bench.exe
AES/CCM benchmarks...
2.7 GHz cpu frequency
3.00491 cycles per byte (cpb)
856.904 MiB per second (MiB)
Usually you benchmark a library with CTR mode. For example, all of the SUPERCOP benchmarks are performed using the mode. You can switch to CTR mode by including "modes.h"
, and then:
CTR_Mode<AES>::Encryption cipher;
cipher.SetKeyWithIV(key, key.size(), key);
Finally, the same test using CTR mode:
$ ./bench.exe
AES/CTR benchmarks...
2.7 GHz cpu frequency
0.568922 cycles per byte (cpb)
4525.97 MiB per second (MiB)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…