针对密集读操作的场景显著地提高性能。
This aims to provide a significant performance boost in read-mostly scenarios
这个属性会忽略Web浏览器的读操作。
为了实现这个策略，简单地将所有的读操作传递到源，并返回结果。
For this policy, all read operations are simply passed on to the sources, and results are returned.
因而，读操作与日志写和缓冲池中的数据页的写操作之间存在竞争。
Thus, the read operations compete with log writing and the write operation for data pages from the buffer pool.
在数据库读操作成功之后，它循环遍历结果集并收集帐户数据信息。
After a successful database read operation, it iterates on the result set and collects the individual account data information.
还支持异步地分散读操作与写操作，该操作需要大量字节缓存。
Scattering reads and writes, which take an array of byte buffers, are also supported asynchronously.
使用键执行随机读操作的最常见rpg方法是CHAIN操作。
The most common RPG method for performing a random read using a key is the CHAIN operation.
我在此处假设读操作(作为api层的入口点)不会对数据库调用写操作。
I am making the assumption here that the read operation (as an entry point to the API layer) is not in turn invoking write operations on the database.
共享内存区域的一个作用是充当缓冲区，以减少对磁盘的读操作。
One purpose of the shared memory area is to act as a buffer, minimizing the necessity for further reads from disk.
所有的写操作都被分发到主节点，而读操作可以在任何节点上进行。
All writes are directed to the primary node, from where they are replicated while reads can be performed on any node.
对于读操作，索引custname1更小一些，因此可能带来更好的性能。
For read operations, index custname1 is smaller and therefore potentially better performing.
通过使用乐观并发控制，数据库管理器在完成读操作之后可以立即释放行或页锁。
With optimistic concurrency control, the database manager releases the row or page locks immediately after a read operation.
由于SELECTINTO返回单个行，因此它不能用于其他R PG读操作。
Because the SELECT INTO returns a single row it cannot be used for other RPG read operations.
甚至可以编写加强的方面来确保读操作的控制流中不会调用对同一对象的写操作！
You could even write enforcement aspects to ensure that a write operation on the same object would not be invoked while in the control-flow of a read operation!
rw参数，使用它指明预抓取数据是为了执行读操作，还是执行写操作。
The rw parameter, which you use to indicate whether the data is being pulled in for Read or preparing for a Write operation.
读操作的完整硬盘寻道时间是 7.4毫秒，而写操作是 7.9 毫秒。
The full disk seek time is 7.4 milliseconds for reads and 7.9 milliseconds for writes.
结果，它一般需要大量的物理磁盘读操作来保证实现一致的低事务响应时间。
As a result, a high number of physical disk reads are usually required to ensure consistently low transaction response times.
当我们查看一下查询计划的时候，我们看到有50- 100k的读操作。
When I look at the query plans for these, I'm seeing 50-100k reads.
R PG程序更新通过键访问的行之前，必须执行一个读操作，以便锁定该行，进行更新。
Before an RPG program updates a row accessed by a key it must perform a read operation to lock the row for update intent.
DPF对于以读操作为主的工作负载很有用，包括数据仓库环境中常见的工作负载。
DPF can be useful for read-intensive workloads, including those common to data warehouse environments.
特别是，拥有读操作屏障允许你切换到较简单的GC算法—更易于并发、扩展和强壮。
In particular, having a read-barrier allows you to switch to a simpler GC algorithm - and a simple algorithm can be more easily made parallel, scalable, concurrent and robust.
读操作是使用本地存储执行的(除非本地磁盘发生故障，那时通过辅助节点访问辅助存储)。
Read operations are performed using local storage (unless the local disk has failed, at which point the secondary storage is accessed through the secondary node).
它们在连接的两端使用两个标准的文件描述符—一个只执行读操作，另一个只执行写操作。
Both use two standard file descriptors on each end of the connection-one exclusive to read and another exclusive to write operations.
OpenLDAP软件和包提供了创建目录信息树（一个主要进行读操作的数据库）的工具。
The OpenLDAP software and the packages it interfaces with provide tools to create a Directory Information Tree, a read-mostly database.
意思是很多异步读无顺序完成(像在3.6.2讨论的)，通过异步读操作无序的返回字节块流。
This means that several asynchronous reads complete out of order (as discussed before in section 3.6.2), and byte chunk streams returned by the pending reads will not be processed in order.
但是，假若我们想全部利用IOCP服务器的潜力，我们应该有很多的异步读操作等待数据的到达。
But if we want to use the IOCP server's full potential, we should have several pending asynchronous reads waiting for data to arrive.
在某些情况下，如果读操作远远大于写操作，volatile变量还可以提供优于锁的性能优势。
In situations where reads greatly outnumber writes, volatile variables may also provide a performance advantage over locking.
事务2 (TX2)并没有被禁止做同样的事情，并在最开始的时候便对值1000进行了读操作。
Transaction 2 (Tx2) is not prevented from doing the same thing, and reads the balance initially as 1000.
只有部分数据副本参与更新操作，且/或作为读操作的一部分与其它副本进行联系时，就会出现弱/最终一致性。
Weak/eventual consistency happens when not all data replicas participate in the update operation and/or contacted as part of read operation.
如果读操作的次数要远远超过写操作，与锁相比，volatile变量通常能够减少同步的性能开销。
In cases where reads greatly outnumber writes, volatile variables can often reduce the performance cost of synchronization compared to locking.
应用推荐