会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 8. 发明公开
    • DATABASE MANAGEMENT SYSTEM, COMPUTER, AND DATABASE MANAGEMENT METHOD
    • DATENBANKVERWALTUNGSSYSTEM,COMPUTER UND DATENBANKVERWALTUNGSVERFAHREN
    • EP2843558A1
    • 2015-03-04
    • EP12875047.8
    • 2012-04-27
    • Hitachi, Ltd.The University of Tokyo
    • TOKUDA SeisukeSHIMIZU AkiraYOSHIDA MichikoKAWAMURA NobuoFUJIWARA ShinjiMOGI KazuhikoKITSUREGAWA MasaruGODA Kazuo
    • G06F12/00G06F9/50
    • G06F17/30463G06F9/4843G06F17/30477G06F2209/485
    • A database management system (DBMS) generates a query execution plan including information indicating one or more database (DB) operations necessary to execute the query and executes the query based on the query execution plan. The DBMS dynamically generates the task for executing the DB operation in execution of the query and executes the dynamically generated task. The DBMS performs a determination processing of simultaneous-task-generation number when newly creating a task. The determination processing of simultaneous-task-generation number is to calculate the number of simultaneous task generation, which is the number of tasks that can be generated simultaneously, based on the number of tasks which can be newly generated, a first memory resource amount which is the amount of memory resources necessary to be allocated per task newly generated, and a second memory resource amount which is the number of memory resources that can be newly allocated. The number of tasks generated dynamically and simultaneously is equal to or smaller than the calculated number of simultaneously generatable tasks.
    • 数据库管理系统(DBMS)生成查询执行计划,其包括指示执行查询所必需的一个或多个数据库(DB)操作的信息,并且基于查询执行计划执行查询。 DBMS在执行查询时动态生成执行DB操作的任务,并执行动态生成的任务。 当新创建任务时,DBMS执行同时任务生成次数的确定处理。 同时任务生成号的确定处理是基于可以新生成的任务的数量来计算同时任务生成的数量,即同时生成的任务的数量,第一存储器资源量 是新生成的每个任务需要分配的内存资源量,以及可以新分配的存储器资源的数量的第二存储器资源量。 动态和同时生成的任务数量等于或小于计算出的同时可生成任务的数量。
    • 10. 发明公开
    • MULTI-CORE SYSTEM AND SCHEDULING METHOD
    • 多伦多大学
    • EP2587374A1
    • 2013-05-01
    • EP10853690.5
    • 2010-06-25
    • Fujitsu Limited
    • KURIHARA, KojiYAMASHITA, KoichiroYAMAUCHI, HiromasaSUZUKI, Takahisa
    • G06F9/48G06F9/52
    • G06F9/48G06F9/4881G06F13/366G06F2209/483G06F2209/485
    • Profile information (26) concerning access of peripheral devices by tasks assigned to processor cores is prepared in advance. A monitor (27) monitors access requests to each peripheral device from the tasks under execution at the processor cores. If a task under execution at a processor core #0_(21) issues an access request to a peripheral device A(24) when a task under execution at a processor core #1_(22) has already accessed a peripheral device B(25), contention occurs at a bus. The monitor (27), therefore, prohibits the access request by the task under execution at the processor core #0_(21). A scheduler (28), based on the profile information (26), replaces the task under execution at the processor core #0_(21) with a task that does not cause contention at the bus.
    • 预先准备关于通过分配给处理器核心的任务来访问外围设备的简档信息(26)。 监视器(27)从处理器核心处执行的任务监视对每个外围设备的访问请求。 如果在处理器核心#1_(22)处于执行中的任务已经访问了外围设备B(25)时,在处理器核心#0_(21)下执行的任务向外围设备A(24)发出访问请求, 在公共汽车上发生竞争。 因此,监视器(27)禁止在处理器核心#0_(21)处执行的任务的访问请求。 基于简档信息(26)的调度器(28)用处理器核心#0_(21)处理执行的任务替换不在总线上引起争用的任务。