Skip to content

PQC: Implement draft RFC for ML-KEM with X25519 #65

PQC: Implement draft RFC for ML-KEM with X25519

PQC: Implement draft RFC for ML-KEM with X25519 #65

Triggered via pull request November 6, 2024 15:18
@larabrlarabr
reopened #10
pqc
Status Failure
Total duration 3m 4s
Artifacts

benchmark.yml

on: pull_request
Time and memory usage benchmark
2m 53s
Time and memory usage benchmark
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Memory usage benchmark (attempt #1): performance regression detected for test 'openpgp.encrypt/decrypt (AEAD, text @ 10MB, with streaming)': test/benchmarks/memory_usage.js#L1
Previous value was 136.14 and current value is 163.39. It is 1.200161598354635x worse, exceeding the failure threshold of 1.10.
Time and memory usage benchmark
1 of 2 alerts exceeded the failure threshold `1.10` specified by fail-threshold input: # **Performance Alert** Possible performance regression was detected for benchmark **'Memory usage benchmark'**. Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `1.02`. | Benchmark suite | Current: b2d2d56626f62fe0fead3d514e42ea7e8aecfa52 | Previous: f443c6183e11f5f6879c41d33820a80a07a15ce0 | Ratio | |-|-|-|-| | `openpgp.encrypt/decrypt (AEAD, text, with streaming)` | `91.47` MB (`heapTotal: 17.77, heapUsed: 8.29, external: 7.35, arrayBuffers: 5.19`) | `88` MB (`heapTotal: 17.49, heapUsed: 8.49, external: 7.31, arrayBuffers: 5.19`) | `1.04` | | `openpgp.encrypt/decrypt (AEAD, text @ 10MB, with streaming)` | `163.39` MB (`heapTotal: 63.94, heapUsed: 36.08, external: 59.39, arrayBuffers: 57.27`) | `136.14` MB (`heapTotal: 56.52, heapUsed: 27.46, external: 32.97, arrayBuffers: 30.85`) | `1.20` | This comment was automatically generated by [workflow](https://github.com/ProtonMail/openpgpjs/actions?query=workflow%3APerformance%20Regression%20Test).
Memory usage benchmark (attempt #1): potential performance regression detected for test 'openpgp.encrypt/decrypt (AEAD, text, with streaming)': test/benchmarks/memory_usage.js#L1
Previous value was 88 and current value is 91.47. It is 1.039431818181818x worse, exceeding the warning threshold of 1.02.