如果有很多数据修改操作，而查询较少，那么应该将注意力放在好的写性能上。
If you have very frequent data modification operations and less queries, you should focus on good write performance.
因而，读操作与日志写和缓冲池中的数据页的写操作之间存在竞争。
Thus, the read operations compete with log writing and the write operation for data pages from the buffer pool.
但如果把投入写操作系统的精力用来推行数据标准，那些理想主义者应该会离他们的理想更接近。
But if the same effort in writing operating systems were put into marketing data standards, the idealists would be a step closer to their better world.
在这种模式下，写操作是在数据存储到本地磁盘并镜像到对等节点内存后被确认的。
In this mode, the Write operation is acknowledged after the data is stored on the local disk and mirrored to the peer node's memory.
在一个信号量保护大量数据时，如果一个或多个任务使用它进行写操作，这个信号量就会成为系统瓶颈。
When a semaphore protects a large amount of data, assuming one or more tasks USES it on a write basis, the semaphore becomes a bottleneck within the system.
通常，执行本地写IO的同步操作大于通过TCP/IP传输到备用系统的数据量。
Often the simultaneous operation of performing the local write IO is greater than the transfer of data over TCP/IP to the standby.
执行操作通常会导致读、写或修改一个或多个持久性数据。
Execution of an operation will typically cause one or more persistent data records to be read, written, or modified.
在实现中不要使用安全方法(如GET和HEAD)进行不安全的操作(如，写数据)，这点非常重要。
It's important that implementations do not use safe methods e.g. GET and HEAD to perform unsafe operations e.g.
ChunkWrites：区块写的总数(区块写以排序的写操作形式执行，是最高效的数据库服务器写操作)。
Chunk writes: Total number of chunk writes (chunk writes, performed as sorted writes, are the most efficient writes available to the database server).
如果没有分帧机制，一端接收到的数据可能比另外一端发送的数据多或少(这会将一次写操作划分成多次操作，或者将多次写操作合并到一个读操作中)。
Without framing, a peer may receive more or less than was sent (splitting up a write or aggregating multiple writes into a single read).
该解决方案使用与RAID文件服务器相同的技术，允许整个ZEO数据库集群以冗余的方式操作，并且所有服务器都参与读和写。
It USES the same techniques as a RAID file server to allow an entire cluster of ZEO databases to operate redundantly, with all servers participating in both reads and writes.
每个成员可以同时访问相同的数据库，包括读和写操作。
Each member can simultaneously access the same database for both read and write operations.
因为我们在协议中没有数据库保证能提交或回滚(参阅步骤12)这一点，所以数据库可以不执行任何写人操作。
It might not perform any write operations, because we haven't gotten to the point in the protocol where the database guarantees being able to commit or rollback (see step 12).
将分割镜像初始化为快照时，将执行崩溃恢复，回滚所有未提交的事务，并使数据库可以被所有读或写操作访问。
The initialization of the split mirror as snapshot performs a crash recovery, rolls back all uncommitted transactions, and makes the database available for any read or write operation.
其他想要并发访问相同表中的数据的应用程序不需要与数据库断开连接，并且可以继续进行该表中的读或写操作。
Other applications that want to access data in the same table concurrently do not need to disconnect from the database, and are free to pursue read or write operations in that table.
对于每个集群数据库副本，与写磁盘操作相关的网络流量会加倍。
For each cluster database replica, network traffic associated with write disk operations is approximately doubled.
由于这些进程产生了大量数据，所以允许将所有这些写操作都发生在闪存是不可取的。
Since a huge amount of data is produced by these processes, it is not advisable to allow all of these writes to happen to flash.
使用数据库系统监视器，利用有关从缓冲池进行写操作的快照数据(或事件监视器)信息来帮助您调优该配置参数。
Use the database system monitor to help you tune this configuration parameter using information from the snapshot data (or event monitor) about write activity from a buffer pool.
但是，必须考虑到在不出现事务超时或事务日志写满的情况下数据库能够处理的操作量。
However, it must be taken into account what the database can handle without a transaction timeout or a transaction log full failure.
写操作在本地登记后即返回，这样数据库崩溃或者出现性能问题能有效跟网站相应时间解耦。
Write operations are acknowledged after being journalled locally, so that disruptions in database availability or performance are decoupled from website response times.
另一方面，对不一致数据结构的写操作需要磁盘的固件首先读取两个扇区，修改两个扇区的分区，然后写两个扇区。
Writes of misaligned data structures, on the other hand, require the disk's firmware to first read two sectors, modify portions of both sectors, and then write two sectors.
数据库使问题复杂化，因为它缓存了一些磁盘写操作，这可能会生成一个不一致的快照。
A database complicates the matter, because it caches some disk writes, which may result in an inconsistent snapshot.
我在此处假设读操作(作为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.
当一端对一个套接字执行写操作时，可确保对等端读出的数据大小与此相同(请参见图5)。
When a peer performs a write on a socket, it is guaranteed that this same-sized chunk of data will be read at the peer endpoint (see Figure 5).
可交换的写操作简化了新数据块的创建流程。
Commutative writes also simplify the process of bringing up new partitions.
因为添加和取出数据操作使用相同的互斥锁，所以读取数据的速度会影响写数据的线程访问锁。
Because you're sharing the same mutex for push and pop operations, the data-read speed is somewhat compromised as writer threads access the lock.
最终用户拥有用户数据，并可对其进行写操作。
也可以在数据库系统没有离线的情况下执行离线备份，方法是当复制数据库目录的时候冻结系统（阻塞所有写操作）。
Offline backup can also be performed without bringing the database system offline by freezing the system (blocking all write operations) while copying the database directory.
相反，读者返回基于当前提交的版本的数据；即写操作开始之前的数据。
Instead, readers return data that is based on the currently committed version; that is, data prior to the start of the write operation.
Realm写操作：目前所有Realm实现都支持“读”操作来获取验证和授权数据以执行登录和访问控制。
Realm Write operations: Currently all Realm implementations support 'read' operations for acquiring authentication and authorization data to perform logins and access control.
应用推荐