用于基准代码运行K次的Unix命令。-UnixCommandForBenchmarkingCodeRunningKtimes

13  

try

试一试

$ time ( your commands )

write a loop to go in the parens to repeat your command as needed.

编写一个循环以进入括号中，根据需要重复您的命令。

Update

Okay, we can solve the command line too long issue. This is bash syntax, if you're using another shell you may have to use expr(1).

好的，我们可以解决命令行太长问题。这是bash语法，如果您正在使用另一个shell，您可能必须使用expr(1)。

$ time (
> while ((n++ <100)); do echo "n = $n"; done
> )

real    0m0.001s
user    0m0.000s
sys     0m0.000s

14  

to improve/clarify on Charlie's answer:

改善/阐明查理的答案:

time (for i in $(seq 10000); do ./mycode; done)

5  

Just a word of advice: Make sure this "benchmark" comes close to your real usage of the executed program. If this is a short living process, there could be a significant overhead caused by the process creation alone. Don't assume that it's the same as implementing this as a loop within your program.

只要一句忠告:确保这个“基准”接近你实际使用的程序。如果这是一个短暂的生命过程，那么仅由过程创建就可能造成重大的开销。不要假设这与在程序中实现循环是一样的。

3  

To enhance a little bit some other responses, some of them (those based on seq) may cause a command line too long if you decide to test, say one million times. The following does not have this limitation

为了增强一些其他的响应，其中一些(基于seq的)可能会导致命令行太长，如果您决定测试100万次。以下没有这个限制

time ( a=0 ; while test $a -lt 10000 ; do echo $a ; a=`expr $a + 1` ; done)

2  

Another solution to the "command line too long" problem is to use a C-style for loop within bash:

“命令行太长”问题的另一个解决方案是在bash中使用c样式的for循环:

 $ for ((i=0;i<10;i++)); do echo $i; done

This works in zsh as well (though I bet zsh has some niftier way of using it, I'm just still new to zsh). I can't test others, as I've never used any other.

这在zsh中也可以使用(尽管我打赌zsh使用它的方式更简单，但我对zsh还是很陌生)。我不能测试其他人，因为我从来没有使用过其他的。

0  

If you're worried about the overhead of constantly load and unloading the executable into process space, I suggest you set up a ram disk and time your app from there.

如果您担心不断加载和卸载可执行文件到进程空间的开销，我建议您设置一个ram磁盘，并设置应用程序的时间。

Back in the 70's we used to be able to set a "sticky" bit on the executable and have it remain in memory.. I don't know of a single unix which now supports this behaviour as it made updating applications a nightmare.... :o)

回到70年代，我们曾经能够在可执行文件上设置一个“粘性”位，并将其保留在内存中。我不知道一个unix,现在支持这种行为,因为它更新应用程序一场噩梦....:o)