| /f-stack/app/redis-5.0.5/src/ |
| H A D | redis-benchmark.c | 711 benchmark(title,cmd,len); in main() 735 benchmark("SET",cmd,len); in main() 741 benchmark("GET",cmd,len); in main() 747 benchmark("INCR",cmd,len); in main() 753 benchmark("LPUSH",cmd,len); in main() 759 benchmark("RPUSH",cmd,len); in main() 765 benchmark("LPOP",cmd,len); in main() 771 benchmark("RPOP",cmd,len); in main() 778 benchmark("SADD",cmd,len); in main() 785 benchmark("HSET",cmd,len); in main() [all …]
|
| H A D | Makefile | 188 REDIS_BENCHMARK_NAME=redis-benchmark 189 REDIS_BENCHMARK_OBJ=ae.o anet.o anet_ff.o redis-benchmark.o adlist.o zmalloc.o redis-benchmark.o 259 dict-benchmark: dict.c zmalloc.c sds.c siphash.c 269 …) $(REDIS_CHECK_AOF_NAME) *.o *.gcda *.gcno *.gcov redis.info lcov-html Makefile.dep dict-benchmark
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | cpu-capacity.txt | 25 CPU capacities are obtained by running a suitable benchmark. This binding makes 26 no guarantees on the validity or suitability of any particular benchmark, the 29 * A "single-threaded" or CPU affine benchmark 30 * Divided by the running frequency of the CPU executing the benchmark 33 For the time being we however advise usage of the Dhrystone benchmark. What 36 CPU capacities are obtained by running the Dhrystone benchmark on each CPU at 38 by the frequency (in MHz) at which the benchmark has been run, so that
|
| /f-stack/app/redis-5.0.5/ |
| H A D | .gitignore | 5 redis-benchmark
|
| /f-stack/freebsd/contrib/zstd/programs/ |
| H A D | README.md | 6 - `zstd` : default CLI supporting gzip-like arguments; includes dictionary builder, benchmark, and … 8 - `zstd-small` : CLI optimized for minimal size; no dictionary builder, no benchmark, and no suppor… 64 - __ZSTD_NOBENCH__ : `zstd` cli will be compiled without its integrated benchmark module. 128 CLI includes in-memory compression benchmark module for zstd. 129 The benchmark is conducted using given filenames. The files are read into memory and joined togethe… 130 It makes benchmark more precise as it eliminates I/O overhead. 134 The benchmark measures ratio, compressed size, compression and decompression speed. 207 -b# : benchmark file(s), using # compression level (default: 3) 211 -S : output one benchmark result per input file (default: consolidated result)
|
| H A D | zstd.1.md | 409 benchmark file(s) using compression level # 411 benchmark file(s) using multiple compression levels, from `-b#` to `-e#` (inclusive) 413 minimum evaluation time, in seconds (default: 3s), benchmark mode only
|
| /f-stack/freebsd/contrib/zstd/ |
| H A D | CONTRIBUTING.md | 162 benchmarks on your end before submitting a PR. Of course, you will not be able to benchmark 179 will typically not be stable enough to obtain reliable benchmark results. If you can get your 186 1. The most simple thing you can do to drastically improve the stability of your benchmark is 188 thumb, the smaller the change you are trying to measure, the more samples of benchmark runs 193 benchmark number, you might have more luck by taking the median. The mean is not robust to 195 benchmark achieved on each run since that is likely the fastest your process will be 205 address is directly by simply not including the first `n` iterations of your benchmark in 213 on Windows. You will get more stable benchmark results of you end those processes as well. 232 ### Zstd benchmark 242 specify a running time for your benchmark in seconds (default is 3 seconds). [all …]
|
| H A D | CHANGELOG | 70 cli : -b -d command can now benchmark decompression on multiple files 83 misc: Extend largeNbDicts benchmark to compression 274 cli : new : hidden command `-S`, to benchmark multiple files while generating one result per file 358 cli : new : advanced benchmark command --priority=rt 442 Changed : -i# now selects benchmark time in second 514 New : benchmark mode can select directory as input
|
| H A D | README.md | 36 using [lzbench], an open-source in-memory benchmark by @inikep 74 using [lzbench], an open-source in-memory benchmark by @inikep
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | profile_app.rst | 16 to profile and benchmark an application. 43 Linux ``perf`` tool can be used to profile and benchmark an application. In
|
| /f-stack/freebsd/contrib/zstd/zlibWrapper/ |
| H A D | README.md | 77 The benchmark is conducted using given filenames or synthetic data if filenames are not provided. 79 It makes benchmark more precise as it eliminates I/O overhead. 83 The benchmark tool can be compiled with `make zwrapbench` using [zlibWrapper/Makefile](Makefile).
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | pvp_reference_benchmark.rst | 6 PVP reference benchmark setup using testpmd 9 This guide lists the steps required to setup a PVP benchmark using testpmd as 11 is to have a reference PVP benchmark without using external vSwitches (OVS,
|
| /f-stack/app/redis-5.0.5/deps/ |
| H A D | README.md | 6 * **hiredis** is the official C client library for Redis. It is used by redis-cli, redis-benchmark … 58 4. Check manually that redis-cli and redis-benchmark behave as expecteed, since we have no tests fo…
|
| /f-stack/dpdk/doc/guides/mempool/ |
| H A D | stack.rst | 15 over-provisioned. Users are encouraged to benchmark with multiple mempool types
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | dist_app.rst | 22 This application can be used to benchmark performance using the traffic
|
| H A D | l2_forward_real_virtual.rst | 32 This application can be used to benchmark performance using a traffic-generator, as shown in the :n…
|
| H A D | ipsec_secgw.rst | 94 processing is done entirely in HW. This mode can be used to benchmark the raw 102 benchmark numbers.
|
| H A D | l2_forward_job_stats.rst | 31 This application can be used to benchmark performance using a traffic-generator, as shown in the :n…
|
| H A D | l2_forward_event.rst | 32 This application can be used to benchmark performance using a traffic-generator,
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_17_11.rst | 194 Added a new "PMD cyclecount" benchmark mode to the ``dpdk-test-crypto-perf``
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | intel_vf.rst | 543 …For the expected benchmark performance, you must pin the cores from the Guest OS to the Host OS (t…
|