在一个数据锁存如果LE是低，时钟是在高或低的逻辑电平举行。
The a data is latched if le is low and clock is held at a high or low logic level.
译码电路接收测量端模拟信号，转化为7段显示的数字信号，发送到数据锁存器上。
The A/D decoding circuit received simulation signal form measurement port and converted the signals into data signals which displayed by 7-segment, then signals were sent to data latch.
分析了处理并发事务时现有XML数据锁机制的问题，并提出了自己的XML数据上锁规则。
Analyze the current problems of using lock mechanism when deal with concurrency transactions of XML data.
本文不涉及分布式计算情况下的数据同步、数据锁、多线程下对象状态同步和超长事务等问题。
The synchronization and data lock in distribute enviroment, and long transaction and concurrency in multi-thread enviroment are not our concerns in this article.
每个器件都有一个八位CMOS移位寄存器和CMOS控制电路，八个CMOS数据锁存，八个双极电流吸收达林顿输出驱动器。
Each device has an eight-bit CMOS shift register and CMOS control circuitry, eight CMOS data latches, and eight bipolar current-sinking Darlington output drivers.
我猜测这是由于它的实现比较保守，根据不同条件(比如锁对象数据大小和其他OS特定的特性)及早地关掉了它。
My guess is that it is implemented very conservatively and disabled early based on various conditions like lock object data size and OS specific features.
因为仅在将数据刷新到磁盘时获得锁，所以性能并不会受到很大的影响。
Since the lock is acquired only while flushing data to disk, performance is not extensively affected.
锁并不总是必须控制整个数据资源。
A lock does not always have to control an entire data resource.
最后，我认识到激活锁省略似乎和被锁对象的数据大小有关系。
Finally I came to recognize that there seems to be some relation between the enabling of lock elision and the data size of the locked object.
无锁(lock - free)数据结构和算法。
Nirvanix提供了锁数据到具体实际位置的选择，但是亚马逊没有。
Nirvanix offers the option of locking data into specific physical locations, but Amazon does not.
在此方案中，用户从数据库中检索数据而不加任何锁。
In this scenario, a user retrieves data from the database with no locks.
但是，获取并在数据库中保留锁仅仅是高并发性任务的一个部分。
But obtaining and holding locks in the database is only part of the high-concurrency story.
每个数据库都有一个锁列表，锁列表包含了并发连接到该数据库的所有应用程序所持有的锁。
There is one lock list per database, and it contains the locks held by all applications concurrently connected to the database.
不断地会有许多线程需要这些锁保护的数据，所以可以想象，当要取得这个锁的时候，可能不得不等候其他人用完它。
The data protected by these locks is needed constantly by many threads, and you can expect that when you go to acquire this lock, you may have to wait until someone else is done with it.
并发控制在业务事务术语中通常涉及生成和维护数据存储上的锁，例如关系数据库。
Concurrency control in business transaction terms usually involves generating and maintaining locks on data stores, such as relational databases.
通过此策略，由于您未对数据保持读取锁，因此在执行更新操作时遇到失效数据异常的机率会增加。
With this strategy, because you are not holding read locks on data, the chance of getting stale data exceptions when you execute the update operations increases.
现在我们已经准备就绪，可以从newstaff表导出数据，并同步捕获数据库锁快照了。
We are now ready to export the data from the NEWSTAFF table, and to simultaneously capture a database lock snapshot.
这一次，DB 2引擎获得一个互斥捕捉，用于同步地移动数据，因此当锁超时没有发生时，其他任务将等待数据移动的完成。
At this time, an exclusive seize is acquired by the DB2 engine to synchronously move the data, so while a lock time-out will not occur, other jobs will wait for the move to complete.
只有在事务提交时才需要数据库写入锁，以确保原子地更新已修改的项，而不受到并发更新的干扰。
Database write locks are needed only at transaction commit time to ensure that the modified items are updated atomically without interference from concurrent updaters.
存放数据的时候，他先要获得互斥锁，再往总线上写数据，最后再释放互斥锁。
When publishing its data, it would acquire a mutex, do writes to the bus, and release the mutex.
事务锁(数据库锁)是单个事务工作单元内出现的锁。
Transaction locks (database locks) are those that occur within a single transactional unit of work.
锁快照包含数据库摘要信息、应用程序信息，当然还有锁信息。
The lock snapshot includes database summary information, application information and, of course, the lock information.
要支持高数据库并发性，则需要减少数据库锁，并尽可能缩短保持资源的时间。
To support high database concurrency, you need to reduce database locks and hold resources for as little time as possible.
数据库用于在其中维护锁信息的空间的相关数据库参数可能需要调整。
The related database parameters for the space where the database maintains the lock information might need to be adjusted.
MAXLOCKS定义了应用程序持有的锁列表的百分比，在数据库管理器执行锁升级之前必须填充该锁列表。
MAXLOCKS defines a percentage of the lock list held by an application that must be filled before the database manager performs lock escalation.
在手动删除数据库锁文件之前，请务必确认在数据库机器上没有JVM在运行。
Be sure to verify that no JVMs are running on the database machine before manually removing a database lock file.
不可变数据是不能更改的，因此读取不可变数据无需用到锁，即使有多个线程读取时也是如此。
Immutable data cannot be changed and thus reading immutable data does not require locks, even when multiple threads are reading.
同乐观锁定策略相比，物理数据库锁需要持续较长的时间，因此应用程序性能和吞吐量很可能会受到影响。
As physical database locks are held for a longer time duration than with an optimistic locking strategy, there is more of a chance for performance and throughput being impacted.
因为添加和取出数据操作使用相同的互斥锁，所以读取数据的速度会影响写数据的线程访问锁。
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.
应用推荐