每组测试中，可接受用户响应时间都为一秒。
For both set of tests one second was used as the acceptable user response time.
针对单用户响应时间问题的调试方法。
80%的最终用户响应时间花在前端上。
80% of the end-user response time is spent on the front-end.
端口加密对最终用户响应时间的影响随用户数增大而增大。
There's an incremental impact of port encryption on end-user response time.
探针（probe）响应时间（和用户响应时间）
对于任何Web应用程序，用户响应时间都取决于以下因素的综合。
As with any Web application, user response time depends on a combination of factors.
保持Cookie大小以尽量减低对用户响应时间的影响尽可能低。
Keep cookie sizes as low as possible to minimize the impact on the user response time.
对于所有三种活动用户负载，用户响应时间均小于 0.20秒。
User response times were less than 0.20 seconds for all three active user loads.
这一指标模拟了最终用户的响应时间，并且是反映最终用户响应时间的最佳指标。
This metric simulates and is the best indicator of end user response time.
我们通过用户收集关于终端用户响应时间改进的反馈(通过站点中每个页面底部的反馈链接)。
We collected feedback about the improved end-user response time from our users (through the feedback link that appears at the bottom of every page on our site).
这意味着当总体系统利用率小于60%时，您可以启用端口加密，而不用担心在用户响应时间方面的性能影响。
This means that you can turn on port encryption without worrying about a performance impact for your users' response time when the overall system utilization is in the less than 60% range.
请记住80 90%的最终用户响应时间用于下载页中的所有组件：图像、样式表、脚本，闪速，等。
Remember that 80-90% of the end-user response time is spent downloading all the components in the page: images, stylesheets, scripts, Flash, etc.
该测试场景比较各种负载情况下的平均用户响应时间、探针响应时间、系统cpu利用率、占用的内存和磁盘利用率。
This test scenario compared average user response times, probe response time, system CPU utilization, memory used, and disk utilization at various loads.
此时程序的“实际执行时间”，即整体执行时间与等待用户响应时间之差，才能够真实地反映用户可察觉的系统处理能力。
So the subtraction of user input time from total time, namely the "real execution time", can truly reflect the user-perceived performance.
更快的数据访问可以让应用程序运行的更快，因此能获得更好的用户响应时间，更好的应用程序吞吐量，更强大的支持更多用户的能力。
Faster data access makes your applications run faster, so you have better user response time, better application throughput, and a better ability to support more users.
图4显示的是，用户响应时间小于三秒情况下，LotusDomino8.5.2上的经典讨论数据库和XPages讨论数据库。
Figure 4 shows the classic discussion database and the XPages discussion database on Lotus Domino 8.5.2 with user response times of less than three seconds.
您还可以了解到系统配置中的变动如何影响最终用户的响应时间。
You can also see how the variations in system configurations affect the end user's response time.
最终用户会发现探针响应时间测试非常有趣，并且可以从这些信息中获得最大受益。
End users find the probe response time tests interesting and they benefit the most from looking at this information.
在试图查看在线订单历史记录时，用户会遇到响应时间过长的问题。
Customers are experiencing slow response time when trying to view the history of there online orders.
图3展示了用电子表格分析用户和响应时间的方法，这只是为了完整起见，实际上这种方法不值得推荐。
Figure 3 shows a spreadsheet analysis of users and response times, but this is here for completeness and is not recommended.
许多组织通过测量最终用户的响应时间来获得总体的性能情况。
Many organizations measure end user response time to get an overall perspective of performance.
经典讨论数据库显示，在支持200个用户且响应时间小于一秒的情况下，经典讨论数据库IOP更少。
The classic discussion database showed fewer IOPs for the 200 users supported with response times less than one second.
用户HTTP请求的响应时间也会加快。
不幸的是，需求通常会自动识别为用户需求，例如与特定运营所请求的用户或响应时间相关的功能。
Unfortunately, requirements are often automatically identified with user requirements, such as the function related to a use case or the response time requested for a specific operation.
静态编译可以产生最佳的交互式性能，因为没有运行时编译行为来影响用户预期的响应时间。
Interactive performance is best covered by static compilation because no run-time compilation activity interferes with the user's response-time expectations.
很少有用户能够忍受太长的响应时间。
例如，定义Web应用程序策略时最好是根据对最终用户的响应时间，而不是最大的CPU使用阈值。
For example, it is better to define a Web application's policy in terms of response time to the end user instead of maximum CPU utilization threshold.
很重要保持Cookie的大小以尽量减低对用户的响应时间的影响尽可能低。
It's important to keep the size of cookies as low as possible to minimize the impact on the user's response time.
对于200个并发用户的平均请求响应时间是1,381ms。
The average request response time for 200 concurrent users is 1,381 ms.
个并发用户的平均响应时间是1,321ms。
The average request response time for 200 concurrent users is 1,321 ms.
应用推荐