Searched refs:benchmarking (Results 1 – 25 of 32) sorted by relevance
12
7 # performance impact on running systems. When benchmarking new features
17 3. API: include headers should be suitable for benchmarking and testing code
196 something subtle merged is extensive benchmarking. You will be doing us a great favor if you200 you can:) We've adding some things to think about when benchmarking below in the Benchmarking214 benchmarking machine. A virtual machine, a machine with shared resources, or your laptop218 Of course, benchmarking can be done on non-hyper-stable machines as well. You will just have to266 Also check our LLVM's guide on benchmarking here: https://llvm.org/docs/Benchmarking.html271 and then additionally also specify the `-b#` option. Doing this will run our benchmarking pipeline273 benchmarking script works, you can check out programs/benchzstd.c329 4. Run your benchmarking script from your terminal window337 5. Once you run your benchmarking script, switch back over to instruments and attach your343 6. You profiler will now start collecting metrics from your benchmarking script. Once[all …]
101 .PHONY: benchmarking102 benchmarking: automated_benchmarking target
23 bridge/switch). The tests will use the IPv6 benchmarking working
27 "Turns off bug reporting entirely (useful for benchmarking).")
26 // experiments and benchmarking data.
199 // FIXME: This needs more targeted benchmarking.
30 // experiments and benchmarking data.
18 3. API: include headers should be suitable for benchmarking and testing code
112 "for benchmarking the allocator or instrumentator.")
628 32696:128:0:40:M1460: Spirent:Avalanche::Spirent Web Avalanche HTTP benchmarking engine
22 // Based on the LSD (loop-stream detector) queue size and benchmarking data.
27 // Based on the LSD (loop-stream detector) queue size and benchmarking data.
26 // Based on the LSD (loop-stream detector) queue size and benchmarking data.