-
### Problem
Compile times are something we care about, but we're not measuring them systematically, so we have little visibility over them.
### Potential solution
Building the benchmarks is a…
-
cc @dpetrisko
I'll use this issue to collect benchmarks from Dan. These should be examples where Vivado produces mappings that Dan suspects we can improve upon.
-
**10 threads were used for 0.2.0+ (prior versions could not use multithreading)** However, given the 3 simultaneous download limit, I doubt we're effectively using more than 3 threads.
> 49, 24…
-
**Is your feature request related to a problem? Please describe.**
The results for KICS accuracy benchmark are based on `v1.2.x` of KICS which is from [**2021**](https://github.com/Checkmarx/kics/rel…
-
I'd love to see how rtoml v0.11 (specifically https://github.com/samuelcolvin/rtoml/pull/78 where the GIL pool was removed from pyo3) effects performance.
-
# Description
The objective of this issue is to investigate and identify the most effective tools, techniques, and methodologies for benchmarking testing. These tests will serve as a baseline for c…
-
Je note ici les bonnes pratiques pour le benchmark à compléter.
- Utiliser le même itéré initial pour toutes les expérimentations que l'on compare entre-elles
- Passer les mêmes les options pour l…
ocots updated
2 hours ago
-
There are a lot of alternate ways to do the things we are doing with this package. We should document performance and validation with integration test cases.
This will point out performance flaws …
-
Follow-up to #68109, it would be nice if we tracked the size of the toolchain binaries (or the entire archive).
We already track binary size of a bunch of tests on https://perf.golang.org/dashboard…
-
Bring benchmarks up to paper quality:
- [ ] Multiple trials with average and stddev
- [ ] Warmup trials
- [ ] Report memory using profiler instead of (unreliable) `process.memoryUsage().heapUsed`