Because each application that attaches to a database requires some private memory to be allocated, allowing a larger number of concurrent applications will use more memory.
由于需要给连接到数据库的每个应用程序分配一些私有内存，因此允许有更多并发应用程序将意味着用去更多内存。
This time can be significantly reduced if you use raw devices and if you use concurrent access.
如果您使用原始设备，或者使用并发访问，那么就可以极大地减少这一时间。
Administrators are going to see very noticeable improvements in the number of concurrent users that they can support, message throughput, and more efficient use of server assets.
管理员将看到能够支持的并发用户数量和消息吞吐量有显著的改进，并且能够更高效地使用服务器资源。
For faster failover time the best configuration is to use DMS tablespaces and raw devices, and even better allow concurrent access to the disks.
为了获得更快的故障转移时间，最佳配置是使用dms表空间和原始设备，甚至最好允许对磁盘的并发访问。
With a traditional concurrent environment, you might use a solution such as a semaphore that allows processes to determine whether a variable is 'in use' or can be updated.
在传统并行环境中，您可以使用信号量这样的解决方案，允许进程确定一个变量是否 “处于使用中”，还是可更新。
I conclude this introduction to JCSP with a simple example that demonstrates the use of JCSP guards to facilitate non-determinism in concurrent applications.
我用一个简单的示例，演示如何用JCSP警卫实现并发应用程序中的非确定性，借此总结对JCSP的介绍。
Although easy to use, this parameter is global and does not let you specify a specific number of concurrent requests for each target service.
尽管该参数易于使用，但它是全局性的，不允许为每个目标服务指定并发请求数量。
Therefore, you should use concurrent access for faster failover time.
因此，您将使用并发访问以获得更快的故障转移时间。
While described in the "Concurrent Collections" tip (see Resources), the use of the interface is not limited to concurrency.
虽然这个接口是在“并发集合”技巧(请参阅参考资料)中描述的，但它的应用并不限于并发。
Given the relative complexity of managing concurrent updates, we make one related recommendation: Where possible use stateless semantics.
考虑到管理并发更新的相对复杂性，我们提出一个相关的建议：尽可能使用无状态语义。
Many concurrent applications will benefit from their use.
许多并发应用程序将从对它们的使用中获得好处。
When having duplicate rows in the lock table (see the Create a DB2 table for resource locking section), concurrent use of the resource is possible.
如果锁表中有重复的行(参见为资源锁定创建一个DB 2表一节)，就可以对资源进行并发使用。
If you use a language like Scheme there are some examples of a concurrent extension.
如果您使用像Scheme的语言，那么有一些并行扩展的实例。
Sophisticated branching and graphical merge tools enable concurrent access to files and efficient use of time.
高级的分支和图形化合并工具支持对文件的并发访问，以及对时间的有效使用。
Most times we use Hibernate's automatic versioning and detached objects to achieve optimistic concurrent control and high performance an.
大多数时间我们使用Hibernate的自动版本和分离对象来实现乐观并发控制和高性能。
So for example, instead of concurrent linked lists, we use dual concurrent lock circular arrays, so we have the benefits of non blocking concurrency without object creation.
因此，相对于并发链表，我们采用了二重并发锁循环数组（dual concurrent lock circular arrays），这样无需创建对象就能享受到非阻塞并发带来的好处。
When reorganizing XML indexes, database administrators can use the allow write ACCESS clause in the reorg indexes command to allow concurrent writes on the table.
在重组xml索引时，数据库管理员可以通过在REORGINDEXES命令中使用ALLOWWRITEaccess子句允许并发的写操作。
For example, we are using the concurrent techniques in Jetty, but we do not use many of the standard concurrent data structures as they create too many objects.
比如说，我们在Jetty中使用了并发技术，但却并没有使用常见的标准并发数据结构，因为这会创建太多的对象。
This talk covers how to use Erlang to implement reliable, highly - concurrent HTTP-based services using the Yaws web server.
该演讲包括如何利用Erlang来实现可靠、高度并行、基于HTTP、使用YawsWeb服务器的服务。
This platform enables concurrent use of various sensor types, such as active and passive RFID tags or condition sensors.
这个平台允许同时使用多种传感器类型，比如主动式或被动式rfid标签或环境传感器。
That means application 1 may use INDEX 1, while application 2 uses INDEX 2, but concurrent use of INDEX 1 in both applications is not allowed.
这意味着，应用程序1可能使用索引 1，同时应用程序2使用索引 2，但是不允许两个应用程序中同时使用索引 1 。
The use of optimistic locking offers more concurrent access to the data.
乐观锁定的使用能实现更多地同时数据访问。
The s lock allows concurrent applications that use read-only queries to access the target table, but applications attempting to write data to the table are prevented from doing so.
s锁允许使用只读查询的并发应用程序访问目标表，但是防止应用程序写数据到表中。
Should I use async or Task to handle a lot of concurrent operations?
我应该使用异步任务处理大量的并发操作？
The device, capable of handling 2,500 users, one million concurrent sessions and 25,000 new sessions per second, is marketed for use in campus networks, distributed environments and data centers.
该设备，可处理2500,100万并发会话及25 000每秒新建会话，标记为用于园区网络、分布式环境及数据中心。
Use the "nonstrict-read-write" strategy if your data is read-mostly or concurrent cache access and update is rare.
如果你的数据读很多或者很少有并发缓存访问和更新，那么可以使用“nonstrict - read - write”策略。
Even for most enterprise applications the use of the concurrent-mark-sweep collector (also known as the low-pause collector) will reduce pauses to levels that are acceptable for most applications.
甚至对大部分企业级应用程序来说，并行标记扫描(concurrent - mark - sweep)回收器(也叫低暂停回收器，low - pausecollector)的应用也已经把暂停降低到了一个大多数应用可以接受的级别上。
He can use the concept of feedforward, concurrent, and feedback control to identify measures for deterring or reducing employee theft.
他可以利用前馈，同期和反馈控制的概念来鉴定防止或减少员工偷窃的方法。
He can use the concept of feedforward, concurrent, and feedback control to identify measures for deterring or reducing employee theft.
他可以利用前馈，同期和反馈控制的概念来鉴定防止或减少员工偷窃的方法。
应用推荐