| 1. | Number of soap method invocations started per second
每秒启动的soap方法调用数。 |
| 2. | System calls - for i o related problems
系统调用数-用于与i / o相关的问题 |
| 3. | No other samples , such as cpu , page faults , or system calls are collected
而不收集其他样本，如cpu 、页错误或系统调用数。 |
| 4. | The charts in figure 1 and figure 2 show the throughput in calls per second , normalized to the 1 - thread
图1和图2中的图表以每秒调用数为单位显示了吞吐率，把不同的实现调整到1线程 |
| 5. | Therefore , number of calls in the report will not agree with the actual number of times the code block executed
编译的函数中。因此，报告中的调用数会与执行的代码块的实际次数不一致。 |
| 6. | The order of the delegates in the array is the same order in which the current delegate invokes the methods that those delegates represent
数组中委托的顺序与当前委托调用数组中那些委托所表示方法的顺序相同。 |
| 7. | They are the routines that are called a few thousand times a second , so making the routine as tight as possible really helped the performance of the game
这些程序每秒钟要调用数千次，因此，尽可能的简洁将有助于提高游戏的性能。 |
| 8. | These included number of directory services calls , number of database calls , amount of memory used , and path length number of instructions executed
其中包括目录服务调用数、数据库调用数、内存使用量和路径长度（执行的指令数） 。 |
| 9. | If this is not possible , try reducing the number of calls between the managed and unmanaged boundary , with your code doing more work between calls
如果不可能做到这点，请尝试减少托管和非托管边界之间的调用数，从而让代码在调用之间完成更多工作。 |
| 10. | Figure 3 shows the four metrics that we tracked for each single click analysis : number of instructions , memory , number of directory services ldap calls , and database calls
图3展示了为每个单击分析跟踪的四个度量：指令数、内存、目录服务( ldap )调用数和数据库调用数。 |
