Automatic parallelism tuning for apply processes
    11.
    发明授权
    Automatic parallelism tuning for apply processes 有权
    自动并行调整适用流程

    公开(公告)号:US09063773B2

    公开(公告)日:2015-06-23

    申请号:US13949594

    申请日:2013-07-24

    CPC classification number: G06F9/466 G06F9/5083 G06F17/30371

    Abstract: Techniques are provided for automatic parallelism tuning. At least one batch of change records is assigned to one or more apply processes in a set of active apply processes. A first throughput value is periodically determined based on a number of processed change records in a first time interval. An increment adjustment is periodically performed, including adding an additional apply process, determining a second throughput value, and removing the additional apply process from the set of active apply processes if the second throughput value is not greater than a previous first throughput value by at least an increment threshold. A decrement adjustment is periodically performed, including removing an apply process, determining a third throughput value, and replacing the removed apply process in the set of active apply processes if the third throughput value is not greater than the previous first throughput value by at least a decrement threshold.

    Abstract translation: 提供了自动并行调谐技术。 至少一批更改记录被分配给一组活动应用进程中的一个或多个应用进程。 基于在第一时间间隔中的处理的改变记录的数量来周期性地确定第一吞吐量值。 定期执行增量调整,包括添加附加的应用过程,确定第二吞吐量值,以及如果第二吞吐量值不大于先前的第一吞吐量值至少至少在一组活动应用进程中移除附加应用进程 增量阈值。 如果第三吞吐量值不大于先前的第一吞吐量值,则定期执行递减调整,包括去除应用进程,确定第三吞吐量值,以及替换所述一组活动应用进程中的已移除的应用进程, 递减阈值

    CLIENT AND SERVER INTEGRATION FOR REPLICATING DATA
    12.
    发明申请
    CLIENT AND SERVER INTEGRATION FOR REPLICATING DATA 有权
    用于替换数据的客户端和服务器集成

    公开(公告)号:US20150032695A1

    公开(公告)日:2015-01-29

    申请号:US13951281

    申请日:2013-07-25

    CPC classification number: G06F17/30578 G06F17/00

    Abstract: Techniques are provided for client and server integration for scalable replication. A replication client transmits change records to a database server over a stream. The database server determines at least one batch comprising change records for at least one transaction. The database server generates dependency data for at least one change record in a batch based on at least one constraint identifier for at least one column. The database server determines an ordered grouping of the change records based on an operation type of each change record and the dependency data of each change record, wherein change records sharing operation types are grouped together unless a division based on the dependency data is determined. The database server generates a reordered transaction comprising a plurality of reordered operations based on the ordered grouping of the change records of the particular batch.

    Abstract translation: 为客户端和服务器集成提供了可扩展复制技术。 复制客户端通过流将更改记录传输到数据库服务器。 数据库服务器至少确定一个包含至少一个交易的更改记录的批次。 数据库服务器基于至少一个列的至少一个约束标识符来为批次中的至少一个改变记录生成依赖性数据。 数据库服务器基于每个改变记录的操作类型和每个改变记录的依赖性数据来确定改变记录的有序分组,其中改变记录共享操作类型被分组在一起,除非确定基于依赖性数据的划分。 数据库服务器基于特定批次的改变记录的有序分组来生成包括多个重新排序的操作的重排序事务。

    Client-Side Handling Of Transient Duplicates For Row-Level Replication
    13.
    发明申请
    Client-Side Handling Of Transient Duplicates For Row-Level Replication 有权
    用于行级复制的客户端处理瞬态重复

    公开(公告)号:US20140081907A1

    公开(公告)日:2014-03-20

    申请号:US13622276

    申请日:2012-09-18

    CPC classification number: G06F17/30575 G06F17/30309

    Abstract: Transient duplicate key violations of unique key constraints are handled during row updates. Row changes are buffered until a point is reached that those changes are safe to execute. Row changes are effectively reordered to avoid constraint violations during execution of updates. In response to receiving a constraint key violation from a server after an attempted update, a client locally stores a record containing information regarding the failed update. Later, in response to the lack of receipt of an error in response to another update to the same column of the same table, the client uses the information in this record to instruct the server to attempt to repeat a failed update that previously attempted to change the value of a row to a value that was present in a uniqueness-constrained column at the time of the failure, but is no longer present due to the successful update.

    Abstract translation: 在行更新期间处理对唯一密钥约束的瞬态重复密钥违规。 行更改缓冲,直到达到这些更改才能执行的安全性。 行更改被有效地重新排序,以避免在执行更新期间发生约束违规。 响应于在尝试更新之后从服务器接收到约束密钥冲突,客户端本地存储包含关于故障更新的信息的记录。 之后,为了响应对同一表的同一列的另一次更新而收到错误的响应,客户端使用该记录中的信息来指示服务器尝试重复以前尝试更改的故障更新 一行的值在故障时存在于唯一性受限列中但由于更新成功而不再存在的值。

Patent Agency Ranking