Concurrent read-only access to the same container is safe.
对同一个容器进行并发的只读访问是安全的。
With this type of lock, concurrent applications can read from or write to the locked table.
有了这一类型的锁，并发应用程序就可以读或写已锁定的表。
When a table holds a Z lock, no concurrent application can read or update data in that table.
当表持有z锁时，任何并发应用程序都不能读取和更新该表中的数据。
When a table holds an IX lock, the lock owner and concurrent applications can read and update data in that table.
当表持有IX锁时，锁拥有者和并发应用程序可以读和更新该表中的数据。
At the start of an ALLOW NO ACCESS load operation, the utility may force concurrent applications that are trying to read from or write to the target table.
在ALLOWNOACCESS加载操作的开始，该工具可能会压制那些试图读或写目标表的并发应用程序。
The atomic read-modify-write combination shows up in many concurrent algorithms.
许多并发算法中都显示了原子的读-修改-写组合。
On the standby node, it has access to the shared enhanced-concurrent volume group, but only in a passive, read-only mode.
在备用节点上，可以访问共享的增强型并发卷组，但是只能采用被动只读模式。
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锁允许使用只读查询的并发应用程序访问目标表，但是防止应用程序写数据到表中。
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.
特别是，拥有读操作屏障允许你切换到较简单的GC算法—更易于并发、扩展和强壮。
Use the "nonstrict-read-write" strategy if your data is read-mostly or concurrent cache access and update is rare.
如果你的数据读很多或者很少有并发缓存访问和更新，那么可以使用“nonstrict - read - write”策略。
Use the "nonstrict-read-write" strategy if your data is read-mostly or concurrent cache access and update is rare.
如果你的数据读很多或者很少有并发缓存访问和更新，那么可以使用“nonstrict - read - write”策略。
应用推荐