可以评价的基础以支持并发用户的预期数量。
An infrastructure that can scale to support the anticipated number of concurrent users.
在每个阶段使用100个并发用户，见表4。
One hundred concurrent users are used at each of the stages shown in Table 4.
最大的线程池限制是并发用户的最大理论数量。
The maximum thread pool limit is your theoretical maximum number of concurrent users.
个并发用户的平均响应时间是1,321ms。
The average request response time for 200 concurrent users is 1,321 ms.
如果期望1000个并发用户，将该参数设置为50。
This parameter should be set to 50 if you are expecting 1000 concurrent users.
最初发布的性能数据显示一个支持200位并发用户的配置。
The initial published performance data shows a configuration that supports 200 concurrent users.
应用程序在多个并发用户访问时必须极其稳定，且不能牺牲速度。
The application must be extremely stable with numerous users logged in simultaneously. Speed must not be sacrificed.
这个经典的讨论应用程序数据库可扩展至 200个并发用户。
The classic discussion application database scaled up to 200 concurrent users.
对于200个并发用户的平均请求响应时间是1,381ms。
The average request response time for 200 concurrent users is 1,381 ms.
混合工作负载最好的性能也出现在有150个并发用户时，见图4。
The best performance with a mixed workload was also achieved with 150 concurrent users, as shown in Figure 4.
这些测试运行显示了评价储存库中并发用户的数量与资源数量的效果。
These test runs show the effect of scaling the number of concurrent users and the number of resources in the repository.
每个区间显示的是增加一组并发用户后一小时内状态稳定后的平均水平。
Each interval shows the average of the one-hour steady state of each incremental set of concurrent users.
这样使得服务器可以在启动后立即创建处理大量并发用户所必需的连接。
This causes the server to create the necessary connections to handle a large number of concurrent users immediately after startup.
例如，模拟5个并发用户，需要指定5个Thread Group。
For example, to emulate 5 concurrent users, 5 Thread Groups were specified.
该组件按照测试计划的要求进行重复，以模拟一个特定数目的并发用户。
This component was repeated as required in a test plan to emulate a specific number of concurrent users.
并发用户的数目(它影响DB 2代理程序的数量)决定需要多少内存。
The number of concurrent users (with its impact on the number of DB2 agents) determines how much more memory is required.
测试分别采用25、50、75、100、125和150个并发用户。
Tests were conducted with 25, 50, 75, 100, 125, and 150 concurrent users.
系统的平均响应时间在多至1000个并发用户时应小于一秒。
The average response time of the system shall be less than one second with up to 1,000 simultaneous users.
系统应支持1000个并发用户同时查询数据库，而不会发生拥塞或数据丢失。
The system shall support 1,000 simultaneous users, all doing queries against the database at the same time, without crashing or losing data.
如果并发用户的数量超过100，性能有所下降，这可以是负载平衡的一种候选方案。
If the number of concurrent users exceeds 100 and there is performance degradation, this would be a candidate for load-balancing.
GBWeb服务器，4xcpu，为超过100个并发用户提供了稳定的响应时间。
The 4 GB Web servers, 4xcpu, with consistent response time for 100 + concurrent users.
测试证明，并发用户对性能的影响在本质上与大型数据库对性能的影响存在很大的差异。
The nature of the performance impact of concurrent users proved to be quite different from that of large databases.
另一方面，因为不涉及数据库服务器，它对于几乎没有并发用户的程序是相当好的选择。
On the other hand, because no database server is involved, it's a fairly good choice for a program with very few simultaneous users.
基于性能测试的结果，我们发现了资源的增长随着并发用户的增长，会导致硬盘负荷的增长。
Based on the performance test results, we found that an increase in resources along with increase in concurrent users causes an increase in the load on the hard disc.
因为我的设计目标是只针对一个并发用户，我觉得可以省略许多似乎不必要的文件锁定代码。
Because I designed it for a maximum of one simultaneous user, I felt I could dispense with a lot of the file-locking code that might otherwise be necessary.
在此负载水平上的性能分析显示，XPages运行时本身不限制应用程序并发用户的增加。
Performance analysis conducted at that load indicates that the XPages runtime itself did not limit the scaling of concurrent users on this application.
对于使用Domino服务器，Sun机器已经证明其支持大量并发用户的CPU可伸缩性。
Sun machines have already proven their CPU scalability in supporting a high number of concurrent users with Domino server partitions.
截至到 200 个并发用户，经典和XPages讨论数据库的处理器利用率都一样。
The processor utilizations were was about the same between the classic and the XPages discussion data bases until 200 users.
方式：指定了锁的拥有者所允许的访问类型，以及对锁定数据资源的并发用户许可的访问类型。
Mode: Specifies the type of access allowed for the lock owner as well as the type of access permitted for concurrent users of the locked data resource.
我们还将讨论设防的包装器在可伸缩性方面为支持大量并发用户的联邦服务器带来的一些好处。
We also discuss the scalability benefits the fenced wrapper can bring to federated servers supporting a high number of concurrent users.
应用推荐