会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明申请
    • Method and system for faster instance startup for large resource configurations
    • 用于更快速启动大型资源配置的方法和系统
    • US20070233640A1
    • 2007-10-04
    • US11395613
    • 2006-03-30
    • Tirthankar LahiriBharat BaddepudiPoojan Kumar
    • Tirthankar LahiriBharat BaddepudiPoojan Kumar
    • G06F17/30G06F12/00
    • G06F17/3048
    • A method for starting up a database system, comprising allocating memory spaces for three buffers; initializing two of the buffers; partially initializing the third buffer where the third buffer is larger than the other two; instructing the memory manager to initialize the remainder of the third buffer in the background process; performing recovery operations; and opening the database system for use. The database is operated in an open phase while the remainder of the third buffer is initialized in the background and ran in parallel to the recovery operation that may extend beyond the completion of opening the database. Thus opening the database prior to completion of full initialization and initializing the third buffer in the background improves the startup time of the database which becomes significant when the size of the third buffer is very large (e.g., 500 GB+).
    • 一种用于启动数据库系统的方法,包括为三个缓冲器分配存储器空间; 初始化两个缓冲区; 部分地初始化第三缓冲器,其中第三缓冲器大于其他缓冲器; 指示存储器管理器在后台进程中初始化第三缓冲器的剩余部分; 执行恢复操作; 并打开数据库系统使用。 数据库处于开放阶段,而第三个缓冲区的其余部分在后台进行初始化,并且与恢复操作并行运行,该恢复操作可能超出打开数据库的完成时间。 因此,在完成初始化并在后台初始化第三缓冲区之前打开数据库改善了当第三缓冲器的大小非常大(例如,500GB +))时数据库的启动时间变得显着。
    • 4. 发明授权
    • Method and system for faster instance startup for large resource configurations
    • 用于更快速启动大型资源配置的方法和系统
    • US07467279B2
    • 2008-12-16
    • US11395613
    • 2006-03-30
    • Tirthankar LahiriBharat C V BaddepudiPoojan Kumar
    • Tirthankar LahiriBharat C V BaddepudiPoojan Kumar
    • G06F12/06
    • G06F17/3048
    • A method for starting up a database system, comprising allocating memory spaces for three buffers; initializing two of the buffers; partially initializing the third buffer where the third buffer is larger than the other two; instructing the memory manager to initialize the remainder of the third buffer in the background process; performing recovery operations; and opening the database system for use. The database is operated in an open phase while the remainder of the third buffer is initialized in the background and ran in parallel to the recovery operation that may extend beyond the completion of opening the database. Thus opening the database prior to completion of full initialization and initializing the third buffer in the background improves the startup time of the database which becomes significant when the size of the third buffer is very large (e.g., 500 GB+).
    • 一种用于启动数据库系统的方法,包括为三个缓冲器分配存储器空间; 初始化两个缓冲区; 部分地初始化第三缓冲器,其中第三缓冲器大于其他缓冲器; 指示存储器管理器在后台进程中初始化第三缓冲器的剩余部分; 执行恢复操作; 并打开数据库系统使用。 数据库处于开放阶段,而第三个缓冲区的其余部分在后台进行初始化,并且与恢复操作并行运行,该恢复操作可能超出打开数据库的完成时间。 因此,在完成初始化并在后台初始化第三缓冲区之前打开数据库改善了当第三缓冲器的大小非常大(例如,500GB +))时数据库的启动时间变得显着。
    • 9. 发明授权
    • Distributed consistent grid of in-memory database caches
    • 分布式一致的内存数据库缓存网格
    • US08401994B2
    • 2013-03-19
    • US12562928
    • 2009-09-18
    • Chi HoangTirthankar LahiriMarie-Anne NeimatChih-Ping WangJohn MillerDilys ThomasNagender BandiSusan Cheng
    • Chi HoangTirthankar LahiriMarie-Anne NeimatChih-Ping WangJohn MillerDilys ThomasNagender BandiSusan Cheng
    • G06F17/00
    • G06F17/30312G06F12/084
    • A plurality of mid-tier databases form a single, consistent cache grid for data in a one or more backend data sources, such as a database system. The mid-tier databases may be standard relational databases. Cache agents at each mid-tier database swap in data from the backend database as needed. Consistency in the cache grid is maintained by ownership locks. Cache agents prevent database operations that will modify cached data in a mid-tier database unless and until ownership of the cached data can be acquired for the mid-tier database. Cache groups define what backend data may be cached, as well as a general structure in which the backend data is to be cached. Metadata for cache groups is shared to ensure that data is cached in the same form throughout the entire grid. Ownership of cached data can then be tracked through a mapping of cached instances of data to particular mid-tier databases.
    • 多个中间层数据库形成用于一个或多个后端数据源(例如数据库系统)中的数据的单一,一致的高速缓存网格。 中间层数据库可以是标准关系数据库。 每个中间层数据库的缓存代理根据需要从后端数据库交换数据。 高速缓存网格中的一致性由所有权锁定维护。 高速缓存代理阻止数据库操作,将修改中间层数据库中的缓存数据,除非可以为中间层数据库获取缓存数据的所有权。 缓存组定义可以缓存哪些后端数据,以及要缓存后端数据的一般结构。 共享缓存组的元数据,以确保数据在整个网格中以相同的格式缓存。 然后可以通过将缓存的数据实例映射到特定中间层数据库来跟踪缓存数据的所有权。