全部

1·Better support for concurrency.

更好地支持并发。

2·Concurrency state of the union.

并集(union)的并发状态。

3·Chapter 13 covers Concurrency.

第十三章涵盖了并发。

4·Clojure's flavors of concurrency.

Clojure的并发特色。

5·Who really needs concurrency?

谁真正需要并行？

6·The later delivers much better concurrency.

处理后者的更好方式是并发。

7·Operations are designed for concurrency.

操作设计应考虑并发性。

8·On the downside, you need to consider concurrency.

缺点是，您需要考虑并发性。

9·Possible concurrency problems from lock conflicts.

可能由于锁冲突而导致的并发问题。

10·Yet concurrency is important in any modern system.

但是，并发在现代任何一个系统总都是非常重要的。

并发性

1·When mutable state goes away, almost all concurrency problems go away with it.

可变状态消失时，差不多所有的并发性问题也随之消失。

2·Shares some or all of the resources used by the system (i.e., concurrency).

分享一些或所有的系统使用的资源(例如：并发性)。

3·Even in the absence of system failures, there is another risk worth discussing in the above code — concurrency.

甚至在系统没有发生故障时，上面讨论的代码还有另一种风险——并发性。

4·These registry variables can improve concurrency, but can also impact the behavior of the application.

这些变量可以改善并发性，但是也会影响到应用程序的行为。

5·One symptom of insufficient concurrency and insufficient connection pool size is an idle CPU.

并发性不足和连接池大小不足的一个症状是CPU闲置。

并行性

1·To avoid this problem, you should apply an access intent policy that supports optimistic concurrency.

要避免这个问题，您就需要应用访问目的策略，来支持优化的并行性。

2·In typical usage, processes are used to support concurrency.

在典型使用中，进程用于支持并行性。

3·MochiWeb makes use of the process system to support the concurrency, and USES messages to help process the requests and accumulate the results.

MochiWeb利用进程系统支持并行性，利用消息来帮助处理请求和收集结果。

4·Internally Erlang handles the concurrency issue by creating small lightweight executions called processes.

Erlang在内部通过创建称为进程的小型轻量级执行来处理并行性问题。

5·It makes use of many of the features of the Erlang that have been covered in this article, including the use messaging and processes to provide high performance with a high level of concurrency.

它利用了本文所述的许多erlang特性，包括使用消息传递和进程来提供高性能与高级并行性。

并发数

1·Increasing the concurrency beyond this value will increase the transaction response time as threads compete for CPU time, and not actually yield any throughput improvement.

当并发数增加到超过该值时，由于线程争用CPU时间，所以事务响应时间将增加，因而实际上并未带来任何吞吐量方面的改进。

2·If our transaction is CPU-bound, then the productive concurrency is likely to be at most two or three times the number of available processors.

如果我们的事务是CPU限制的，则生产并发数可能最多比可用处理器数多两三倍。

3·The Maximum Messages value is set on the listener port, along with the Maximum Sessions concurrency setting.

在侦听器端口设置最大消息值及最大会话并发数。

4·Unfortunately, it is difficult to estimate the amount of concurrency supported by a single dispatcher thread on this kind of system.

遗憾的是，难以评估这种系统中单个调度程序线程支持的并发数。

5·Page Load Time = (Number of Requests / Concurrency) * Latency + Page Total Size / Bandwidth

页面加载时间 = （请求数 / 并发数）* 延迟时间 + 页面总大小 / 带宽

(1)concurrency control并发控制