liboqs benchmarking still running 0.9.0-rc1

[SWilson4]

See https://openquantumsafe.org/benchmarking/visualization/2024-04-02/speed_kem.json.

I think I fixed this by reordering the Docker cleanup commands in the scripts run by cron jobs on various platforms. We'll see when the tests run next, I guess.

TODO in future profiling updates/fixes: add the trigger scripts to GitHub somewhere so we can have proper version control for them.

[SWilson4]

It turns out that this was not an issue due to cron jobs; we just haven't pushed the oqs-perf image since liboqs main was at 0.9.0-rc1. Oops...

This could be easily (temporarily) fixed by simply pushing a new image to Docker Hub, but at this point we've had so many issues with profiling that I would rather rewrite the infrastructure setup to (attempt to) avoid this popping up again in the future.

[baentsch]

would rather rewrite the infrastructure setup

ACK. I'm turning off the AWS VMs running profiling then.

[baentsch]

One more thought: OK to close all open issues given they're no longer relevant given a new system is being done? Or do you want to keep them as "bad examples"/what to avoid @SWilson4 ? Makes for shorter OQS meeting invites :)

[baentsch]

@SWilson4 I was doing some cleanup and came across this issue: How are you coming along with the new baentschmarking ? Shall we close this issue without action or should I re-activate something now that there are new algs available for testing?

[SWilson4]

@SWilson4 I was doing some cleanup and came across this issue: How are you coming along with the new baentschmarking ? Shall we close this issue without action or should I re-activate something now that there are new algs available for testing?

I've taken the lack of activity on #112 to indicate that there currently isn't enough interest in b(a)en(ts)chmarking to justify the time required to revitalize the subproject.

It would be nice to have something, though, especially as we now have new algorithms that haven't yet been benchmarked in liboqs. Perhaps I should interpret the lack of discussion to indicate that the status quo for benchmarking was OK (barring bugs) and we should just update the oqs-perf image and fire up the VMs again, being careful to avoid old issues.