Less aggressive LRU flushing can improve transaction performance.
更缓慢的LRU刷新可以提高事务性能。
Both toolkits support these activities via close integration with IBM Tivoli Monitoring for Transaction Performance.
这两个工具包通过与IBMTivoli事务性能监控的紧密结合来完成这些功能。
Then, you can use Tivoli Monitoring for Transaction Performance to monitor the various transactions and see how they actually perform.
然后，使用Tivoli事务性能监测来观察各事务并明白他们是如何执行的。
For example, for many server applications it's not important if the server takes longer to start up: what's important is the run rate of transaction performance after startup.
例如，如果这个服务器要花费很长时间来启动，那么对于许多服务器应用软件来说就不重要：重要的启动之后事务性能的运行速率。
Of course, you should have an additional thread in the application to capture transaction correlation data so that neither the core transaction performance nor response time is affected.
当然，这些应用程序中还应该有额外的线程来获取事务关联数据以免核心事务性能和响应时间受到影响。
For example, IBM Tivoli Monitoring for transaction Performance monitors transactions across multiple tiers in your architecture, and can pinpoint the exact location of a bottleneck.
比如说，IBMTivoli MonitoringforTransaction Performance监视你的体系架构中多个层次上的交易，并查明的瓶颈的确切位置。
Optimizations in Informix 11.7 have dramatically improved query and transaction performance, and have leveraged physical changes to the POWER7 platform to make transparent improvement possible.
Informix 11.7中的优化可以显著提高查询和事务性能，已经将物理更改运用到POWER 7平台，尽可能实现透明改进。
For example, if your database is used for transaction processing and heavy decision-support (DSS) queries, you can be sure that a non-scheduled DSS query will trash your transaction performance.
例如，如果您的数据库用于事务处理和繁重的决策支持(DSS)查询，则可以确定非预定的DSS查询将牺牲您的事务性能。
The ORM restriction might require you to accept yet another trade-off — maintainability and technology selection for better performance with transaction support.
ORM限制可能要求您接受另一个弊端 —可维护性和通过事务支持获得更好性能的技术选择。
Transaction management supported by the EJB container can also affect performance.
EJ b容器支持的事务管理也可以影响性能。
You usually need this level of detail for specialized purposes; such as performance measurements, transaction audit trails, or transactions that take less than a second.
对于专门的目的，通常需要这个细节级别；比如性能测量、事务审计跟踪或者小于一秒的事务。
DB2 EEE architecture can improve the performance of decision support and online transaction processing systems.
DB 2EEE体系结构可以提高决策支持和联机事务处理系统的性能。
Transaction duration is limited by the application server's performance and the EISs deployed in the same administrative domain.
应用服务器的性能和部署在同一管理域的EIS会限制事务的持续时间。
With our test configuration, we found an across-the-board improvement in performance when turning on transaction logging.
使用我们的测试配置，我们发现，打开事务日志时整体性能都得到了提高。
Unless you cannot avoid processing the incoming messages and database update in a single unit of work, consider using local transaction for performance reasons.
除非您不能避免在单个工作单元中处理收到的消息和数据库升级，否则因为性能的原因要考虑用局部事务处理。
Decomposition of a transaction is important in determining where a bottleneck or performance degradation is occurring.
对事务进行分解在确定何处会发生瓶颈或性能下降问题是十分重要的。
Turning on transaction logging is not used just for the performance gains.
启用事务日志功能并不仅仅是为了提升性能。
This parameter is required to improve performance of DB2 when operating with the particular transaction manager.
在操作特定的事务管理器时，需要此参数来改进DB2的性能。
In some circumstances you might need to trade some level of performance for a slower ACID-based transaction strategy.
在某些情况下，您可能需要牺牲一些性能，使用较慢的基于ACID的事务策略。
Add comments to the index to indicate why it was created, for example, to help the performance of transaction XYZ.
添加关于索引的注释，指示创建的原因，例如，用于帮助提高事务xyz的性能。
In case the transaction log becomes a performance bottleneck, striped disks can be used to increase the write throughput, as described in [9].
如果事务日志成为一个性能瓶颈，可以使用带状磁盘来提高写入流量，如[9]所述。
Instead, record each transaction two times and measure the performance separately.
相反，您可以将每次交易记录两次，并单独地测试性能。
In the case of the High Performance transaction strategy, the duration of the transaction is measured in seconds, not minutes.
在使用高性能事务策略的情况下，事务的持续时间以秒(而不是分钟)来计算。
Transaction logging appeared to have a small but significant effect on overall performance and for the two major transaction types.
事务日志对总体性能和两个主要事务类型的影响比较小但非常重要。
Transaction duration is the most important factor in performance, and an application's overall performance can be improved by shortening each individual transaction it USES.
事务持续时间是最重要的性能因素，并且，缩减所有个体事务的持续时间将改善应用程序的总体性能。
Optimistic transaction locking is generally preferred for its performance characteristics and reduced likelihood of deadlock situations.
乐观事务锁定通常以其高性能和死锁发生可能性较低的特点而被首选使用。
A transaction is a specific group of test elements whose performance you are interested in.
一个事务是一个特定的测试元素组，您可能对其所含的测试元素的性能感兴趣。
Other features, like multiple MAIL.BOX databases, eliminating the extra overhead of unread marks, and transaction logging have also improved performance.
其他特性（比如多MAIL.BOX数据库）消除了未读标记带来的额外开销，并且通过事务日志改进了性能。
The performance improves when the size of the transaction slice is increased.
增加事务片的大小会提高性能。
The results indicate that there is a beneficial performance effect from having transaction logging enabled.
结果表明启用事务日志能够提升性能。
应用推荐