会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明申请
    • LOST WRITE PROTECTION VIA STREAM-BASED REPLICATION
    • 通过基于流行的复制丢失写保护
    • US20090319525A1
    • 2009-12-24
    • US12144613
    • 2008-06-23
    • Gregory ThielAndrew E. Goodsell
    • Gregory ThielAndrew E. Goodsell
    • G06F7/02
    • G06F11/0751G06F11/0727
    • Architecture for detecting lost writes using timestamps. During a replication process, lost writes in data replicated from a stream can be detected by noting discrepancies between the timestamps of data in the replica and timestamps associated with the corresponding data from the source in original data store. A lost write either in the original data store or in the replica data store can be inferred by comparing these timestamps with the timestamps in a number of other replica data stores. Additionally, check entries can be added to the replicas by the original data store to allow expanded comparison between recently modified data and the source data in the original data store. The check entries can be added to the replication journal after a time delay, thereby increasing effectiveness of the check by decreasing the likelihood that caching in the hardware will defeat the test.
    • 用于使用时间戳检测丢失的写入的架构。 在复制过程中,可以通过记录副本中的数据的时间戳和与来自原始数据存储中的源的相应数据相关联的时间戳之间的差异来检测从流复制的数据中的丢失写入。 可以通过将这些时间戳与许多其他副本数据存储中的时间戳进行比较来推断在原始数据存储器中或复制数据存储器中的丢失写入。 此外,检查条目可以由原始数据存储添加到副本,以允许最近修改的数据与原始数据存储中的源数据之间的扩展比较。 检查条目可以在延迟之后添加到复制日志中,从而通过减少硬件中缓存失败的可能性来提高检查的有效性。
    • 3. 发明授权
    • Delaying database writes for database consistency
    • 延迟数据库写入数据库一致性
    • US08768890B2
    • 2014-07-01
    • US11685871
    • 2007-03-14
    • Laurion D. BurchallAndrew E. GoodsellBrett A. Shirley
    • Laurion D. BurchallAndrew E. GoodsellBrett A. Shirley
    • G06F17/30
    • G06F17/30368G06F11/1471G06F11/2038G06F17/30371G06F2201/80
    • A continuous set of committed transactions can be lost without destroying the integrity of the database, by deferring the writing of the database pages stored in cache to the database on stable storage. A waypoint tracks a point in the transaction log following which transactions have not been applied to the database on stable storage and thus records after the waypoint are not needed for recovery to a consistent database. When there is a failover of an active database on Node A to a passive database on Node B, log records are compared starting with the most current and moving backwards and the point at which divergence in the log occurs is determined. When the lost portion of the log occurs after the point indicated by after the waypoint, the database is recoverable by log-based incremental reseed.
    • 通过将存储在缓存中的数据库页面写入稳定存储器上的数据库,可以丢失一组连续的已提交事务,而不会破坏数据库的完整性。 航路点跟踪事务日志中的一个点,其中哪些事务尚未应用于稳定存储上的数据库,因此在恢复到一致的数据库后不需要航点的记录。 当节点A上的活动数据库故障切换到节点B上的被动数据库时,日志记录将从最新和向后移动以及发生日志发散的点进行比较。 当日志的丢失部分发生在航点之后指示的点之后,数据库可以通过基于日志的增量重新进行恢复。
    • 4. 发明申请
    • Delaying Database Writes For Database Consistency
    • 延迟数据库写入数据库一致性
    • US20080228834A1
    • 2008-09-18
    • US11685871
    • 2007-03-14
    • Laurion D. BurchallAndrew E. GoodsellBrett A. Shirley
    • Laurion D. BurchallAndrew E. GoodsellBrett A. Shirley
    • G06F12/00
    • G06F17/30368G06F11/1471G06F11/2038G06F17/30371G06F2201/80
    • A continuous set of committed transactions can be lost without destroying the integrity of the database, by deferring the writing of the database pages stored in cache to the database on stable storage. A waypoint tracks a point in the transaction log following which transactions have not been applied to the database on stable storage and thus records after the waypoint are not needed for recovery to a consistent database. When there is a failover of an active database on Node A to a passive database on Node B, log records are compared starting with the most current and moving backwards and the point at which divergence in the log occurs is determined. When the lost portion of the log occurs after the point indicated by after the waypoint, the database is recoverable by log-based incremental reseed.
    • 通过将存储在缓存中的数据库页面写入稳定存储的数据库,可以丢失一组连续的已提交事务,而不会破坏数据库的完整性。 航路点跟踪事务日志中的一个点,其中哪些事务尚未应用于稳定存储上的数据库,因此在恢复到一致的数据库后不需要航点的记录。 当节点A上的活动数据库故障切换到节点B上的被动数据库时,日志记录将从最新和向后移动以及发生日志发散的点进行比较。 当日志的丢失部分发生在航点之后指示的点之后,数据库可以通过基于日志的增量重新进行恢复。
    • 6. 发明授权
    • Block cache size management via virtual memory manager feedback
    • 通过虚拟内存管理器反馈阻止缓存大小管理
    • US07047387B2
    • 2006-05-16
    • US10620938
    • 2003-07-16
    • Andrew E. Goodsell
    • Andrew E. Goodsell
    • G06F12/12
    • G06F12/0871G06F12/08G06F12/121G06F2212/311
    • A method for calculating a block cache size for a host process or application on a computer based at least upon virtual memory page evictions and/or virtual memory page reclamations for the computer. A virtual memory page eviction is the act of removing the contents of a physical memory page for the purpose of loading it with the contents of another virtual memory page. A virtual memory page reclamation is the return of a page to a working set that was previously removed by the operating system due to memory constraints. The page must not have been evicted. Additional fundamental properties of the application and the computer may be used, such as available physical memory on the computer, total physical memory, and block evictions. A block eviction is the act of removing the contents of a block from the block cache for the purpose of loading it with new contents.
    • 至少基于计算机的虚拟存储器页面驱逐和/或虚拟存储器页面回收来计算计算机上的主机处理或应用程序的块高速缓存大小的方法。 虚拟内存页面删除是删除物理内存页面的内容,以便将其加载到另一个虚拟内存页面的内容。 虚拟内存页面回收是由于内存限制,页面返回到操作系统以前删除的工作集。 页面不能被驱逐出境。 可以使用应用程序和计算机的其他基本属性,例如计算机上的可用物理内存,总物理内存和块驱逐。 块驱逐是从块高速缓存中移除块的内容以将其加载新内容的动作。