Lines Matching refs:benchmark

198 benchmarks on your end before submitting a PR. Of course, you will not be able to benchmark
213 Unfortunately, the most important aspect in being able to benchmark reliably is to have a stable
215 will typically not be stable enough to obtain reliable benchmark results. If you can get your
222 1. The most simple thing you can do to drastically improve the stability of your benchmark is
224 thumb, the smaller the change you are trying to measure, the more samples of benchmark runs
229     benchmark number, you might have more luck by taking the median. The mean is not robust to
231     benchmark achieved on each run since that is likely the fastest your process will be
241     address is directly by simply not including the first `n` iterations of your benchmark in
249 on Windows. You will get more stable benchmark results of you end those processes as well.
250     * If you have multiple cores, you can even run your benchmark on a reserved core to prevent
256 3. To benchmark, you will likely end up writing a separate c/c++ program that will link libzstd.
268 ### Zstd benchmark
278 specify a running time for your benchmark in seconds (default is 3 seconds).
330     * You will want a benchmark that runs for at least a few seconds (5 seconds will