WO2022113578A1 - Management device, system, management method, and recording medium - Google Patents

Management device, system, management method, and recording medium Download PDF

Info

Publication number
WO2022113578A1
WO2022113578A1 PCT/JP2021/038769 JP2021038769W WO2022113578A1 WO 2022113578 A1 WO2022113578 A1 WO 2022113578A1 JP 2021038769 W JP2021038769 W JP 2021038769W WO 2022113578 A1 WO2022113578 A1 WO 2022113578A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
application
job
execution device
execution
Prior art date
Application number
PCT/JP2021/038769
Other languages
French (fr)
Japanese (ja)
Inventor
竜義 大村
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to DE112021006183.6T priority Critical patent/DE112021006183T5/en
Priority to JP2022565115A priority patent/JPWO2022113578A5/en
Publication of WO2022113578A1 publication Critical patent/WO2022113578A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/509—Offload

Definitions

  • the present invention relates to a management device, a system, a management method and a recording medium.
  • HPC High Performance Computing
  • HPC High Performance Computing
  • the file system in HPC is good at reading and writing a large amount of data files by multiple clients.
  • the data stream management system is a dedicated system, it is difficult to use it together with the execution platform of various applications.
  • HPC system can be used together with the execution platform of various applications, but it is not good at handling microdata, where file creation performance is important.
  • a general job scheduler manages a large number of jobs for IoT and AI, which have a short execution time, one by one. Therefore, the job management cost and scheduling cost become enormous, and the throughput decreases.
  • An object of the present invention is to provide a management device, a system, a management method, and a recording medium that enable a more versatile method to reduce the load and improve the throughput when executing a job using microdata. To provide.
  • the management device is a transfer means for transferring the data to an execution device for executing an application when the amount of received data of data related to a predetermined job is equal to or more than a specified value, and transfer of the data.
  • the management method transfers the data to an execution device that executes an application when the received data amount of data related to a predetermined job becomes a specified value or more, and transfers the data. Is completed, the execution device is instructed to execute the job by the application.
  • the management program recorded on a computer-readable recording medium executes an application on the computer when the amount of data received for a predetermined job exceeds a specified value. It is characterized in that a transfer function for transferring the data to the execution device and an instruction function for instructing the execution device to execute the job by the application when the transfer of the data is completed are executed.
  • FIG. 1 shows a configuration example of the management device 10 of the present embodiment.
  • the management device 10 of the present embodiment includes a transfer unit 11 and an instruction unit 12.
  • the transfer unit 11 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value. Further, the instruction unit 12 instructs the execution device to execute the job by the application when the data transfer is completed.
  • the management device 10 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application causes the management device 10. Instructs the execution device to execute the job.
  • the management device 10 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced.
  • the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • FIG. 2 shows an example of the operation of the management device 10 of the present embodiment.
  • the transfer unit 11 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value (step S101). Further, the instruction unit 12 instructs the execution device to execute the job by the application when the data transfer is completed (step S102).
  • the management device 10 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application executes the job. Instruct the execution device.
  • the management device 10 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • the management device 10 transfers data to the execution device that executes the application when the received data amount of the data related to the predetermined job becomes the specified value or more. Transfer and instruct the execution device to execute the job by the application. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • FIG. 3 shows a configuration example of a system including the management device 20 of the present embodiment.
  • the management device 20 is a device that manages the execution of the application in the execution device 40-i.
  • the execution device 40-i (i is an integer of 1 or more and m or less) is a device for executing an application.
  • the management device 20 and the execution device 40-i are connected to each other.
  • the user terminal 60 is connected to the management device 20.
  • the user terminal 60 is a terminal used by a job submitter to cause an application to execute a job.
  • FIG. 4 shows a configuration example of the management device 20 of the present embodiment.
  • the management device 20 of the present embodiment includes a forwarder 21, a conductor 22, and a scheduler 23.
  • the forwarder 21 corresponds to the transfer unit 11 of the management device 10 (FIG. 1) of the first embodiment.
  • the conductor 22 corresponds to the instruction unit 12 of the management device 10 of the first embodiment.
  • the scheduler 23 schedules a job to be executed by the application.
  • the scheduler 23 receives job information indicating information about a job to be executed by the application from the user terminal 60.
  • the job information includes execution application information, maximum number of deployed nodes, firing condition information, required resource information, and notification means information.
  • Execution application information is information indicating an application that executes a job.
  • the maximum number of deployed nodes is the maximum value of the execution device that executes the job.
  • the ignition condition information is information regarding the condition for causing the application to execute the job.
  • the ignition condition information indicates a condition regarding the amount of data received from the user terminal 60 by the management device 20.
  • the management device 20 causes the application to execute a job when the amount of data received from the user terminal 60 exceeds the amount of data indicated by the ignition condition information.
  • the required resource information is information indicating the amount of resources required for the application to execute the job.
  • the notification means information is the type of notification means (for example, file, named pipe, shared memory) when the reception unit 41-i of the execution device 40-i notifies the execution unit 42-i of the start of execution of the application. Etc.).
  • the execution unit 42-i monitors the notification means indicated by the notification means information, and executes the application when the start of execution of the application is notified via the notification means.
  • the notification means is also a write-to interface for writing the data received from the management device 20 by the execution device 40-i.
  • the scheduler 23 When the scheduler 23 receives the job information, it determines the reception number (job ID (Identification)), the authentication token, and the port number of the forwarder 21, and transmits the determined information to the user terminal 60. Further, the scheduler 23 associates these determined information with the job information and stores them in a storage unit (not shown). Further, the scheduler 23 selects the number of execution devices indicated by the maximum number of deployed nodes. The execution device selected here is hereinafter referred to as an execution device candidate. Then, the scheduler 23 starts the application for the selected execution device 40-i, and puts the application in the paused state.
  • job ID Identity
  • the authentication token is used as authentication information when the user terminal 60 accesses the forwarder 21 of the management device 20.
  • the forwarder 21 receives microdata.
  • Microdata includes very small size data.
  • Microdata is transmitted from the user terminal 60 to the port of the port number transmitted from the scheduler 23 to the user terminal 60 in response to the user's operation.
  • a job ID is assigned to the microdata.
  • the forwarder 21 notifies the conductor 22 to that effect.
  • the designated value is a value indicated by the ignition condition information.
  • the ignition condition information is stored in the storage unit in association with the job ID.
  • the amount of received data is managed for each job ID.
  • the conductor 22 When the conductor 22 receives the notification that the data amount of the received microdata exceeds the specified value, the conductor 22 acquires the load status information of each execution device 40-i from the scheduler 23. Further, the conductor 22 determines the execution device 40-i to which the microdata is transferred based on the information on the load status. The conductor 22 determines the execution device 40-i, which has a small load, as the transfer destination of the microdata. The conductor 22 selects the execution device 40-i to which the microdata is transferred from the execution device candidates.
  • the conductor 22 determines the execution device 40-i to which the microdata is transferred, for example, by the following method.
  • the conductor 22 confirms whether there is an execution device 40-i in which the job is not executed. If there is an execution device 40-i in which the job is not executed, the conductor 22 determines the execution device 40-i as the transfer destination of the microdata. If there is no execution device 40-i in which the job is not executed, the conductor 22 determines the execution device 40-i having free resources of the resource amount indicated by the required resource information as the transfer destination of the microdata. If there is no execution device 40-i with free resources in the amount of resources indicated by the required resource information, the conductor 22 micro-distributes the execution device 40-i having the lowest priority of the job being executed among the execution device candidates. Determine as the data transfer destination.
  • the forwarder 21 transmits microdata to the transfer destination execution device 40-i determined by the conductor 22.
  • the forwarder 21 notifies the conductor 22 of the completion of data transfer when the execution device 40-i notifies the completion of reception of microdata.
  • the conductor 22 When the conductor 22 is notified that the data transfer is completed, the conductor 22 notifies the receiving unit 41-i of the executing device 40-i that the application is ready to be executed.
  • the execution device 40-i includes a receiving unit 41-i and an executing unit 42-i.
  • the receiving unit 41-i receives the microdata transmitted by the forwarder 21 of the management device 20. Further, the receiving unit 41-i receives the notification means information. The receiving unit 41-i may obtain the notification means information by referring to the storage unit in which the job information is stored, instead of receiving the notification means information.
  • the receiving unit 41-i When the receiving unit 41-i receives the micro data, it writes the received micro data to the notification means indicated by the notification means information, and notifies the forwarder 21 of the management device 20 of the completion of receiving the micro data.
  • the management device 20 notifies that the receiving unit 41-i is ready to execute the application, the receiving unit 41-i releases the suspension of the application. Then, the receiving unit 41-i notifies the execution unit 42-i of the start of execution of the application via the notification means.
  • Execution unit 42-i executes the application. Further, when the execution of the application is completed, the execution unit 42-i notifies the reception unit 41-i of the end of the application.
  • the receiving unit 41-i puts the application in a paused state when the end of the application is notified.
  • the management device 20 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application causes the management device 20 to execute the data. Instructs the execution device to execute the job.
  • the management device 20 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced.
  • the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • the scheduler 23 of the management device 20 receives job information from the user terminal 60 (step S301).
  • the job information includes execution application information, maximum number of deployed nodes, firing condition information, required resource information, and notification means information.
  • the scheduler 23 Upon receiving the job information, the scheduler 23 activates the forwarder 21, the conductor 22, and the receiving unit 41-i for the job (step S302). Further, the scheduler 23 determines the reception number (job ID), the authentication token, and the port number of the forwarder 21, and transmits the determined information to the user terminal 60 (step S303). Further, the scheduler 23 stores the determined information in the storage unit in association with the job information. Further, the scheduler 23 selects the number of execution devices indicated by the maximum number of deployed nodes. Then, the scheduler 23 starts the application for the selected execution device 40-i, and puts the application in the paused state.
  • the forwarder 21 receives microdata (step S304).
  • Microdata includes very small data files. Microdata is transmitted from the user terminal 60 to the port of the port number transmitted from the scheduler 23 to the user terminal 60 in response to the user's operation. A job ID is assigned to the microdata.
  • the forwarder 21 notifies the conductor 22 to that effect (step S305).
  • the designated value is a value indicated by the ignition condition information.
  • the conductor 22 When the conductor 22 receives the notification that the data amount of the received microdata exceeds the specified value, the conductor 22 acquires the load status information of each execution device 40-i from the scheduler 23. Further, the conductor 22 determines the execution device 40-i to which the microdata is transferred based on the information on the load status. The conductor 22 determines the execution device 40-i, which has a small load, as the transfer destination of the microdata. Then, the conductor 22 transmits the transfer destination information to the forwarder 21 (step S306).
  • the conductor 22 determines the execution device 40-i to which the microdata is transferred, for example, by the method shown in FIG. 7.
  • the conductor 22 confirms whether there is an execution device 40-i in which the job is not executed (step S401). If there is an execution device 40-i in which the job has not been executed (YES in step S401), the conductor 22 determines the execution device 40-i as the transfer destination of the microdata (step S402). If there is no execution device 40-i in which the job has not been executed (NO in step S401), the conductor 22 confirms the free resources of the execution device 40-i. Then, the conductor 22 determines the execution device 40-i (YES in step S403) having free resources of the resource amount indicated by the necessary resource information as the transfer destination of the microdata (step S404).
  • the conductor 22 confirms the priority of the job executed by the execution device candidate. Then, the conductor 22 determines the execution device 40-i having the lowest priority of the job being executed among the execution device candidates as the transfer destination of the microdata (step S405).
  • the forwarder 21 transmits microdata to the execution device 40-i of the transfer destination determined by the conductor 22 (step S307 in FIG. 6).
  • Step S308 When the receiving unit 41-i of the executing device 40-i receives the micro data, the received micro data is written in the notification means indicated by the notification means information, and the forwarding completion of the micro data is notified to the forwarder 21 of the management device 20. (Step S308).
  • the forwarder 21 notifies the conductor 22 of the completion of data transfer when the execution device 40-i notifies the completion of reception of microdata (step S309).
  • the conductor 22 When the conductor 22 is notified that the data transfer is completed, the conductor 22 notifies the receiving unit 41-i of the executing device 40-i that the application is ready to be executed (step S310).
  • the management device 20 notifies that the receiving unit 41-i is ready to execute the application, the receiving unit 41-i releases the suspension of the application. Then, the receiving unit 41-i notifies the execution unit 42-i of the start of execution of the application via the notification means (step S311).
  • Execution unit 42-i executes the application. Further, when the execution of the application is completed, the execution unit 42-i notifies the reception unit 41-i of the end of the application.
  • the receiving unit 41-i puts the application in a paused state when the end of the application is notified.
  • the management device 20 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application executes the job. Instruct the execution device.
  • the management device 20 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • the management device 20 transfers data to the execution device that executes the application when the received data amount of the data related to the predetermined job becomes the specified value or more. Transfer and instruct the execution device to execute the job by the application. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
  • the execution device 40-i of the present embodiment writes the data received from the management device 20 in the notification means indicated by the notification means information. This makes it possible to transfer data by the notification means desired by the user. Further, when a means other than the file is used as the notification means, the load on the file system can be further reduced.
  • the management device or the like may be realized by using at least two or more information processing devices physically or functionally. Further, the management device or the like may be realized as a dedicated device, or a general-purpose device may be used. Further, only a part of the functions of the management device and the like may be realized by using the information processing device.
  • FIG. 8 is a diagram schematically showing a hardware configuration example of an information processing device that can realize the management device and the like of each embodiment of the present invention.
  • the information processing device 90 includes a communication interface 91, an input / output interface 92, an arithmetic device 93, a storage device 94, a non-volatile storage device 95, and a drive device 96.
  • the transfer unit 11 and the instruction unit 12 in FIG. 1 can be realized by the communication interface 91 and the arithmetic unit 93.
  • the communication interface 91 is a communication means for the management device or the like of each embodiment to communicate with an external device at least one of wired and wireless.
  • the management device or the like is realized by using at least two information processing devices, the devices may be connected so as to be able to communicate with each other via the communication interface 91.
  • the input / output interface 92 is a man-machine interface such as a keyboard as an example of an input device and a display as an output device.
  • the arithmetic unit 93 is realized by, for example, an arithmetic processing unit such as a CPU (Central Processing Unit) or a microprocessor, or a plurality of electric circuits.
  • the arithmetic unit 93 can, for example, read various programs stored in the non-volatile storage device 95 into the storage device 94 and execute processing according to the read programs.
  • the storage device 94 is a memory device such as a RAM (RandomAccessMemory) that can be referred from the arithmetic unit 93, and stores programs, various data, and the like.
  • the storage device 94 may be a volatile memory device.
  • the non-volatile storage device 95 is a non-volatile storage device such as a ROM (Read Only Memory), a flash memory, etc., and can store various programs, data, and the like.
  • ROM Read Only Memory
  • flash memory etc.
  • the drive device 96 is, for example, a device that processes data reading and data writing recorded on a recording medium 97, which will be described later.
  • the recording medium 97 is an arbitrary recording medium capable of recording data, such as an optical disk, a magneto-optical disk, or a semiconductor flash memory.
  • a management device or the like is configured by the information processing device 90 illustrated in FIG. 8, and a program capable of realizing the functions described in each of the above embodiments is supplied to the management device or the like. It may be realized by doing.
  • the embodiment can be realized by the arithmetic unit 93 executing the program supplied to the management device or the like. Further, it is also possible to configure some functions of the information processing apparatus 90, not all of the management apparatus and the like.
  • the program may be recorded in the recording medium 97, and the program may be appropriately stored in the non-volatile storage device 95 at the shipping stage, the operation stage, or the like of the management device or the like.
  • a method of installing the program in a management device or the like by using an appropriate jig may be adopted at the manufacturing stage before shipment, the operation stage, or the like.
  • a general procedure such as a method of downloading from the outside via a communication line such as the Internet may be adopted.
  • a management device including an instruction means for instructing the execution device to execute the job by the application when the transfer of the data is completed.
  • Appendix 2 The management device according to Appendix 1, wherein the instruction means determines the execution device to which the data is transferred based on the load status of the execution device.
  • the execution device is A receiving means that receives notification means information indicating the type of the interface to which the data is written and writes the received data to the interface of the type indicated by the notification means information.
  • the system according to Appendix 4 further comprising an execution means for causing the application to execute the job by using the data written in the interface when the execution instruction of the application is received.
  • Appendix 6 The system according to Appendix 5, wherein the interface type is one of a file, a named pipe, and a shared memory.
  • a management method comprising instructing the execution device to execute the job by the application when the transfer of the data is completed.
  • Appendix 8 The management method according to Appendix 7, wherein the execution device to which the data is transferred is determined based on the load status of the execution device.
  • Appendix 9 The management method according to Appendix 7 or Appendix 8, wherein the data includes microdata having a very small size.
  • the execution device is The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
  • Appendix 11 The management method according to Appendix 10, wherein the interface type is one of a file, a named pipe, and a shared memory.
  • the instruction function is a computer-readable recording medium recording a management program according to Appendix 12, characterized in that the execution device to which the data is transferred is determined based on the load status of the execution device.
  • the data is a computer-readable recording medium on which the management program according to Appendix 12 or Appendix 13, characterized in that it contains microdata of very small size, is recorded.
  • the execution device is The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
  • the computer can read the management program according to the appendix 14, characterized in that the application is made to execute the job by using the data written in the interface. Recording medium.
  • Appendix 16 A computer-readable recording medium recording the management program according to Appendix 15, wherein the interface type is one of a file, a named pipe, and a shared memory.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

In order to enable the reduction of burdens and the improvement of throughput when executing jobs in which microdata is used to be realized by a more versatile method, this management device is characterized by comprising: a transfer unit that, when the received data amount of data pertaining to a prescribed job becomes greater than or equal to a designated value, transfers the data to an execution device that executes an application; and an instruction unit that, when transfer of the data is completed, instructs the execution device to execute the job by the application.

Description

管理装置、システム、管理方法および記録媒体Management equipment, systems, management methods and recording media
　本発明は、管理装置、システム、管理方法および記録媒体に関する。 The present invention relates to a management device, a system, a management method and a recording medium.
　ＨＰＣ（High Performance Computing）は、主に、非常に大きなサイズのデータを入出力とするシミュレーションに利用されている（特許文献１）。ＨＰＣにおけるファイルシステムは、多クライアントによる多量データファイルの読み書きが得意である。 HPC (High Performance Computing) is mainly used for simulations that input and output data of a very large size (Patent Document 1). The file system in HPC is good at reading and writing a large amount of data files by multiple clients.
　一方、ＩｏＴ（Internet of Things）やＡＩ（Artificial Intelligence）向けのシステムでは、データ量がごく小さいデータ（マイクロデータという）が扱われている。マイクロデータを扱うファイルシステムでは、頻繁にファイルが作成されるため、ファイルの読み書き性能よりもファイルの作成性能が重要である。マイクロデータを扱うシステムでは、主に、データストリーム管理システムが用いられている（特許文献２）。 On the other hand, systems for IoT (Internet of Things) and AI (Artificial Intelligence) handle data with a very small amount of data (called microdata). In a file system that handles microdata, files are created frequently, so file creation performance is more important than file read / write performance. A data stream management system is mainly used in a system that handles microdata (Patent Document 2).
特表２０１０－５３９５９４号公報Special Table 2010-359594 特表２０１９－５３７０９２号公報Special Table 2019-537092
　データストリーム管理システムは専用システムであるため、様々なアプリケーションの実行基盤と併用することが難しい。 Since the data stream management system is a dedicated system, it is difficult to use it together with the execution platform of various applications.
　また、ＨＰＣシステムは、様々なアプリケーションの実行基盤と併用することができるが、ファイルの作成性能が重要なマイクロデータの扱いが苦手である。 The HPC system can be used together with the execution platform of various applications, but it is not good at handling microdata, where file creation performance is important.
　また、一般的なジョブスケジューラは、実行時間が短時間である、ＩｏＴやＡＩ向けの多量のジョブを、一つずつ管理している。そのため、ジョブの管理コストやスケジューリングコストが膨大になり、スループットが低下する。 In addition, a general job scheduler manages a large number of jobs for IoT and AI, which have a short execution time, one by one. Therefore, the job management cost and scheduling cost become enormous, and the throughput decreases.
　本発明の目的は、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することを可能にする、管理装置、システム、管理方法および記録媒体を提供することにある。 An object of the present invention is to provide a management device, a system, a management method, and a recording medium that enable a more versatile method to reduce the load and improve the throughput when executing a job using microdata. To provide.
　本発明の一態様において、管理装置は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送手段と、前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示手段とを備えることを特徴とする。 In one aspect of the present invention, the management device is a transfer means for transferring the data to an execution device for executing an application when the amount of received data of data related to a predetermined job is equal to or more than a specified value, and transfer of the data. Is provided with an instruction means for instructing the execution device to execute the job by the application when the above is completed.
　また、本発明の他の態様において、管理方法は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送し、前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示することを特徴とする。 Further, in another aspect of the present invention, the management method transfers the data to an execution device that executes an application when the received data amount of data related to a predetermined job becomes a specified value or more, and transfers the data. Is completed, the execution device is instructed to execute the job by the application.
　また、本発明の他の態様において、コンピュータ読み取り可能な記録媒体に記録された管理プログラムは、コンピュータに、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送機能と、前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示機能とを実行させることを特徴とする。 Further, in another aspect of the present invention, the management program recorded on a computer-readable recording medium executes an application on the computer when the amount of data received for a predetermined job exceeds a specified value. It is characterized in that a transfer function for transferring the data to the execution device and an instruction function for instructing the execution device to execute the job by the application when the transfer of the data is completed are executed.
　本発明によれば、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 According to the present invention, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
本発明の第一の実施形態の管理装置の構成例を示す図である。It is a figure which shows the structural example of the management apparatus of 1st Embodiment of this invention. 本発明の第一の実施形態の管理装置の動作例を示す図である。It is a figure which shows the operation example of the management apparatus of 1st Embodiment of this invention. 本発明の第二の実施形態の管理装置を含むシステムの構成例を含む図である。It is a figure which includes the structural example of the system including the management apparatus of the 2nd Embodiment of this invention. 本発明の第二の実施形態の管理装置の構成例を示す図である。It is a figure which shows the structural example of the management apparatus of the 2nd Embodiment of this invention. 本発明の第二の実施形態の実行装置の構成例を示す図である。It is a figure which shows the structural example of the execution apparatus of the 2nd Embodiment of this invention. 本発明の第二の実施形態の管理装置および実行装置の動作例を示す図である。It is a figure which shows the operation example of the management apparatus and execution apparatus of the 2nd Embodiment of this invention. 本発明の第二の実施形態の管理装置の動作例を示す図である。It is a figure which shows the operation example of the management apparatus of the 2nd Embodiment of this invention. 本発明の各実施形態のハードウェア構成例を示す図である。It is a figure which shows the hardware configuration example of each embodiment of this invention.
　［第一の実施形態］
　本発明の第一の実施形態について説明する。 [First Embodiment]
The first embodiment of the present invention will be described.
　図１に本実施形態の管理装置１０の構成例を示す。本実施形態の管理装置１０は、転送部１１と指示部１２とを含む。 FIG. 1 shows a configuration example of the management device 10 of the present embodiment. The management device 10 of the present embodiment includes a transfer unit 11 and an instruction unit 12.
　転送部１１は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送する。また、指示部１２は、データの転送が完了した場合に、アプリケーションによるジョブの実行を実行装置に指示する。 The transfer unit 11 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value. Further, the instruction unit 12 instructs the execution device to execute the job by the application when the data transfer is completed.
　このように管理装置１０を構成することによって、管理装置１０は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。これにより、管理装置１０は、データを受信する都度アプリケーションを実行させる場合に比べて、実行装置へのデータ転送の回数を減らすことができる。その結果、データの転送時間やファイルシステムへの負荷を低減することができる。また、アプリケーションの実行回数を減らすことができるので、ジョブスケジューラの負荷を低減することができる。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 By configuring the management device 10 in this way, the management device 10 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application causes the management device 10. Instructs the execution device to execute the job. As a result, the management device 10 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　次に、図２に本実施形態の管理装置１０の動作の例を示す。 Next, FIG. 2 shows an example of the operation of the management device 10 of the present embodiment.
　転送部１１は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送する（ステップＳ１０１）。また、指示部１２は、データの転送が完了した場合に、アプリケーションによるジョブの実行を実行装置に指示する（ステップＳ１０２）。 The transfer unit 11 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value (step S101). Further, the instruction unit 12 instructs the execution device to execute the job by the application when the data transfer is completed (step S102).
　管理装置１０は、このように動作することによって、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。これにより、管理装置１０は、データを受信する都度アプリケーションを実行させる場合に比べて、実行装置へのデータ転送の回数を減らすことができる。その結果、データの転送時間やファイルシステムへの負荷を低減することができる。また、アプリケーションの実行回数を減らすことができるので、ジョブスケジューラの負荷を低減することができる。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 By operating in this way, the management device 10 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application executes the job. Instruct the execution device. As a result, the management device 10 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　以上で説明したように、本発明の第一の実施形態では、管理装置１０は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 As described above, in the first embodiment of the present invention, the management device 10 transfers data to the execution device that executes the application when the received data amount of the data related to the predetermined job becomes the specified value or more. Transfer and instruct the execution device to execute the job by the application. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　［第二の実施形態］
　次に、本発明の第二の実施形態について説明する。 [Second embodiment]
Next, a second embodiment of the present invention will be described.
　まず、図３に、本実施形態の管理装置２０を含むシステムの構成例を示す。 First, FIG. 3 shows a configuration example of a system including the management device 20 of the present embodiment.
　管理装置２０は、実行装置４０－ｉにおけるアプリケーションの実行を管理する装置である。実行装置４０－ｉ（ｉは１以上ｍ以下の整数）は、アプリケーションを実行する装置である。管理装置２０と実行装置４０－ｉは、互いに接続される。 The management device 20 is a device that manages the execution of the application in the execution device 40-i. The execution device 40-i (i is an integer of 1 or more and m or less) is a device for executing an application. The management device 20 and the execution device 40-i are connected to each other.
　管理装置２０には、利用者端末６０が接続される。利用者端末６０は、アプリケーションにジョブを実行させるためにジョブ投入者が利用する端末である。 The user terminal 60 is connected to the management device 20. The user terminal 60 is a terminal used by a job submitter to cause an application to execute a job.
　次に、図４に、本実施形態の管理装置２０の構成例を示す。本実施形態の管理装置２０は、フォワーダ２１、コンダクタ２２およびスケジューラ２３を含む。フォワーダ２１は、第一の実施形態の管理装置１０（図１）の転送部１１に相当する。また、コンダクタ２２は、第一の実施形態の管理装置１０の指示部１２に相当する。 Next, FIG. 4 shows a configuration example of the management device 20 of the present embodiment. The management device 20 of the present embodiment includes a forwarder 21, a conductor 22, and a scheduler 23. The forwarder 21 corresponds to the transfer unit 11 of the management device 10 (FIG. 1) of the first embodiment. Further, the conductor 22 corresponds to the instruction unit 12 of the management device 10 of the first embodiment.
　スケジューラ２３は、アプリケーションに実行させるジョブをスケジューリングする。スケジューラ２３は、利用者端末６０から、アプリケーションに実行させるジョブに関する情報を示すジョブ情報を受信する。ジョブ情報は、実行アプリケーション情報、最大展開ノード数、発火条件情報、必要リソース情報および通知手段情報を含む。 The scheduler 23 schedules a job to be executed by the application. The scheduler 23 receives job information indicating information about a job to be executed by the application from the user terminal 60. The job information includes execution application information, maximum number of deployed nodes, firing condition information, required resource information, and notification means information.
　実行アプリケーション情報は、ジョブを実行させるアプリケーションを示す情報である。また、最大展開ノード数は、当該ジョブを実行させる実行装置の最大値である。また、発火条件情報は、アプリケーションにジョブを実行させる条件に関する情報である。本実施形態では、発火条件情報は、管理装置２０が利用者端末６０から受信したデータの量に関する条件を示す。管理装置２０は、利用者端末６０から受信したデータの量が、発火条件情報が示すデータ量以上になった場合に、アプリケーションにジョブを実行させる。 Execution application information is information indicating an application that executes a job. The maximum number of deployed nodes is the maximum value of the execution device that executes the job. Further, the ignition condition information is information regarding the condition for causing the application to execute the job. In the present embodiment, the ignition condition information indicates a condition regarding the amount of data received from the user terminal 60 by the management device 20. The management device 20 causes the application to execute a job when the amount of data received from the user terminal 60 exceeds the amount of data indicated by the ignition condition information.
　必要リソース情報は、アプリケーションが当該ジョブを実行するにあたり必要なリソースの量を示す情報である。通知手段情報は、実行装置４０－ｉの受信部４１－ｉが実行部４２－ｉに対してアプリケーションの実行開始を通知する際の、通知手段の種別（たとえば、ファイル、名前付きパイプ、共有メモリなど）を示す情報である。実行部４２－ｉは、通知手段情報が示す通知手段を監視し、アプリケーションの実行開始が通知手段を介して通知された場合に、アプリケーションを実行する。通知手段は、実行装置４０－ｉが管理装置２０から受信したデータを書き込む書き込み先のインタフェースでもある。 The required resource information is information indicating the amount of resources required for the application to execute the job. The notification means information is the type of notification means (for example, file, named pipe, shared memory) when the reception unit 41-i of the execution device 40-i notifies the execution unit 42-i of the start of execution of the application. Etc.). The execution unit 42-i monitors the notification means indicated by the notification means information, and executes the application when the start of execution of the application is notified via the notification means. The notification means is also a write-to interface for writing the data received from the management device 20 by the execution device 40-i.
　スケジューラ２３は、ジョブ情報を受信すると、受付番号（ジョブＩＤ（Identification））、認証トークン、およびフォワーダ２１のポート番号を決定し、決定されたこれらの情報を利用者端末６０へ送信する。また、スケジューラ２３は、決定されたこれらの情報と、ジョブ情報とを対応付けて、記憶部（図示せず）に記憶させる。また、スケジューラ２３は、最大展開ノード数によって示される数の実行装置を選択する。ここで選択された実行装置を、以下、実行装置候補と呼ぶ。そしてスケジューラ２３は、選択された実行装置４０－ｉに対してアプリケーションを起動させ、また、アプリケーションを一時停止状態にさせる。 When the scheduler 23 receives the job information, it determines the reception number (job ID (Identification)), the authentication token, and the port number of the forwarder 21, and transmits the determined information to the user terminal 60. Further, the scheduler 23 associates these determined information with the job information and stores them in a storage unit (not shown). Further, the scheduler 23 selects the number of execution devices indicated by the maximum number of deployed nodes. The execution device selected here is hereinafter referred to as an execution device candidate. Then, the scheduler 23 starts the application for the selected execution device 40-i, and puts the application in the paused state.
　認証トークンは、利用者端末６０が管理装置２０のフォワーダ２１にアクセスする際の認証情報として使用される。 The authentication token is used as authentication information when the user terminal 60 accesses the forwarder 21 of the management device 20.
　フォワーダ２１は、マイクロデータを受信する。マイクロデータは、極小サイズのデータを含む。マイクロデータは、スケジューラ２３から利用者端末６０に送信されたポート番号のポートへ、利用者の操作に応じて、利用者端末６０から送信される。なお、マイクロデータには、ジョブＩＤが付与されている。 The forwarder 21 receives microdata. Microdata includes very small size data. Microdata is transmitted from the user terminal 60 to the port of the port number transmitted from the scheduler 23 to the user terminal 60 in response to the user's operation. A job ID is assigned to the microdata.
　また、フォワーダ２１は、利用者端末６０から受信したマイクロデータのデータ量が指定値以上となった場合に、その旨をコンダクタ２２へ通知する。なお、本実施形態の場合、指定値は、発火条件情報が示す値である。発火条件情報は、ジョブＩＤと対応付けられて記憶部に記憶されている。また、受信データ量はジョブＩＤごとに管理される。 Further, when the amount of microdata received from the user terminal 60 exceeds the specified value, the forwarder 21 notifies the conductor 22 to that effect. In the case of this embodiment, the designated value is a value indicated by the ignition condition information. The ignition condition information is stored in the storage unit in association with the job ID. In addition, the amount of received data is managed for each job ID.
　コンダクタ２２は、受信したマイクロデータのデータ量が指定値以上となった旨の通知を受信すると、各々の実行装置４０－ｉの負荷状況の情報をスケジューラ２３から取得する。また、コンダクタ２２は、負荷状況の情報に基づいて、マイクロデータの転送先の実行装置４０－ｉを決定する。コンダクタ２２は、負荷の小さい実行装置４０－ｉを、マイクロデータの転送先として決定する。なお、コンダクタ２２は、実行装置候補の中から、マイクロデータの転送先の実行装置４０－ｉを選択する。 When the conductor 22 receives the notification that the data amount of the received microdata exceeds the specified value, the conductor 22 acquires the load status information of each execution device 40-i from the scheduler 23. Further, the conductor 22 determines the execution device 40-i to which the microdata is transferred based on the information on the load status. The conductor 22 determines the execution device 40-i, which has a small load, as the transfer destination of the microdata. The conductor 22 selects the execution device 40-i to which the microdata is transferred from the execution device candidates.
　コンダクタ２２は、たとえば、以下のような方法で、マイクロデータの転送先の実行装置４０－ｉを決定する。 The conductor 22 determines the execution device 40-i to which the microdata is transferred, for example, by the following method.
　まず、コンダクタ２２は、ジョブが実行されていない実行装置４０－ｉがあるか確認する。ジョブが実行されていない実行装置４０－ｉがあれば、コンダクタ２２は、当該実行装置４０－ｉを、マイクロデータの転送先として決定する。ジョブが実行されていない実行装置４０－ｉがない場合、コンダクタ２２は、必要リソース情報が示すリソース量の空きリソースがある実行装置４０－ｉを、マイクロデータの転送先として決定する。必要リソース情報が示すリソース量の空きリソースがある実行装置４０－ｉがなければ、コンダクタ２２は、実行装置候補のうち、実行されているジョブの優先度が最も低い実行装置４０－ｉを、マイクロデータの転送先として決定する。 First, the conductor 22 confirms whether there is an execution device 40-i in which the job is not executed. If there is an execution device 40-i in which the job is not executed, the conductor 22 determines the execution device 40-i as the transfer destination of the microdata. If there is no execution device 40-i in which the job is not executed, the conductor 22 determines the execution device 40-i having free resources of the resource amount indicated by the required resource information as the transfer destination of the microdata. If there is no execution device 40-i with free resources in the amount of resources indicated by the required resource information, the conductor 22 micro-distributes the execution device 40-i having the lowest priority of the job being executed among the execution device candidates. Determine as the data transfer destination.
　そして、フォワーダ２１は、コンダクタ２２によって決定された転送先の実行装置４０－ｉへ、マイクロデータを送信する。 Then, the forwarder 21 transmits microdata to the transfer destination execution device 40-i determined by the conductor 22.
　また、フォワーダ２１は、実行装置４０－ｉから、マイクロデータの受信完了が通知された場合、コンダクタ２２へ、データの転送完了を通知する。 Further, the forwarder 21 notifies the conductor 22 of the completion of data transfer when the execution device 40-i notifies the completion of reception of microdata.
　コンダクタ２２は、データの転送完了が通知された場合、実行装置４０－ｉの受信部４１－ｉに、アプリケーションの実行準備ができたことを通知する。 When the conductor 22 is notified that the data transfer is completed, the conductor 22 notifies the receiving unit 41-i of the executing device 40-i that the application is ready to be executed.
　次に、図５を用いて、本実施形態の実行装置４０－ｉについて説明する。実行装置４０－ｉは、受信部４１－ｉと実行部４２－ｉとを含む。 Next, the execution device 40-i of the present embodiment will be described with reference to FIG. The executing device 40-i includes a receiving unit 41-i and an executing unit 42-i.
　受信部４１－ｉは、管理装置２０のフォワーダ２１が送信したマイクロデータを受信する。また、受信部４１－ｉは、通知手段情報を受信する。なお、受信部４１－ｉは、通知手段情報を受信するのではなく、ジョブ情報が記憶された記憶部を参照することによって通知手段情報を入手してもよい。 The receiving unit 41-i receives the microdata transmitted by the forwarder 21 of the management device 20. Further, the receiving unit 41-i receives the notification means information. The receiving unit 41-i may obtain the notification means information by referring to the storage unit in which the job information is stored, instead of receiving the notification means information.
　受信部４１－ｉは、マイクロデータを受信すると、受信したマイクロデータを、通知手段情報が示す通知手段に書き込み、マイクロデータの受信完了を管理装置２０のフォワーダ２１へ通知する。 When the receiving unit 41-i receives the micro data, it writes the received micro data to the notification means indicated by the notification means information, and notifies the forwarder 21 of the management device 20 of the completion of receiving the micro data.
　また、受信部４１－ｉは、アプリケーションの実行準備ができたことが管理装置２０から通知された場合、アプリケーションの一時停止を解除する。そして、受信部４１－ｉは、通知手段を介して、アプリケーションの実行開始を実行部４２－ｉへ通知する。 Further, when the management device 20 notifies that the receiving unit 41-i is ready to execute the application, the receiving unit 41-i releases the suspension of the application. Then, the receiving unit 41-i notifies the execution unit 42-i of the start of execution of the application via the notification means.
　実行部４２－ｉは、アプリケーションを実行する。また、実行部４２－ｉは、アプリケーションの実行が終了すると、アプリケーションの終了を受信部４１－ｉへ通知する。 Execution unit 42-i executes the application. Further, when the execution of the application is completed, the execution unit 42-i notifies the reception unit 41-i of the end of the application.
　受信部４１－ｉは、アプリケーションの終了が通知された場合、アプリケーションを一時停止状態にする。 The receiving unit 41-i puts the application in a paused state when the end of the application is notified.
　このように管理装置２０を構成することによって、管理装置２０は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。これにより、管理装置２０は、データを受信する都度アプリケーションを実行させる場合に比べて、実行装置へのデータ転送の回数を減らすことができる。その結果、データの転送時間やファイルシステムへの負荷を低減することができる。また、アプリケーションの実行回数を減らすことができるので、ジョブスケジューラの負荷を低減することができる。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 By configuring the management device 20 in this way, the management device 20 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application causes the management device 20 to execute the data. Instructs the execution device to execute the job. As a result, the management device 20 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　次に、図６を用いて、本実施形態の管理装置２０および実行装置４０－ｉの動作例について説明する。 Next, an operation example of the management device 20 and the execution device 40-i of the present embodiment will be described with reference to FIG.
　管理装置２０のスケジューラ２３は、利用者端末６０からジョブ情報を受信する（ステップＳ３０１）。ジョブ情報は、実行アプリケーション情報、最大展開ノード数、発火条件情報、必要リソース情報および通知手段情報を含む。 The scheduler 23 of the management device 20 receives job information from the user terminal 60 (step S301). The job information includes execution application information, maximum number of deployed nodes, firing condition information, required resource information, and notification means information.
　スケジューラ２３は、ジョブ情報を受信すると、当該ジョブに関し、フォワーダ２１、コンダクタ２２、受信部４１－ｉを起動する（ステップＳ３０２）。また、スケジューラ２３は、受付番号（ジョブＩＤ）、認証トークン、およびフォワーダ２１のポート番号を決定し、決定されたこれらの情報を利用者端末６０へ送信する（ステップＳ３０３）。また、スケジューラ２３は、決定されたこれらの情報と、ジョブ情報とを対応付けて記憶部に記憶させる。また、スケジューラ２３は、最大展開ノード数によって示される数の実行装置を選択する。そしてスケジューラ２３は、選択された実行装置４０－ｉに対してアプリケーションを起動させ、また、アプリケーションを一時停止状態にさせる。 Upon receiving the job information, the scheduler 23 activates the forwarder 21, the conductor 22, and the receiving unit 41-i for the job (step S302). Further, the scheduler 23 determines the reception number (job ID), the authentication token, and the port number of the forwarder 21, and transmits the determined information to the user terminal 60 (step S303). Further, the scheduler 23 stores the determined information in the storage unit in association with the job information. Further, the scheduler 23 selects the number of execution devices indicated by the maximum number of deployed nodes. Then, the scheduler 23 starts the application for the selected execution device 40-i, and puts the application in the paused state.
　フォワーダ２１は、マイクロデータを受信する（ステップＳ３０４）。マイクロデータは、極小サイズのデータファイルを含む。マイクロデータは、スケジューラ２３から利用者端末６０に送信されたポート番号のポートへ、利用者の操作に応じて、利用者端末６０から送信される。なお、マイクロデータには、ジョブＩＤが付与されている。 The forwarder 21 receives microdata (step S304). Microdata includes very small data files. Microdata is transmitted from the user terminal 60 to the port of the port number transmitted from the scheduler 23 to the user terminal 60 in response to the user's operation. A job ID is assigned to the microdata.
　また、フォワーダ２１は、利用者端末６０から受信したマイクロデータのデータ量が指定値以上となった場合に、その旨をコンダクタ２２へ通知する（ステップＳ３０５）。なお、本実施形態の場合、指定値は、発火条件情報が示す値である。 Further, when the amount of microdata received from the user terminal 60 exceeds the specified value, the forwarder 21 notifies the conductor 22 to that effect (step S305). In the case of this embodiment, the designated value is a value indicated by the ignition condition information.
　コンダクタ２２は、受信したマイクロデータのデータ量が指定値以上となった旨の通知を受信すると、各々の実行装置４０－ｉの負荷状況の情報をスケジューラ２３から取得する。また、コンダクタ２２は、負荷状況の情報に基づいて、マイクロデータの転送先の実行装置４０－ｉを決定する。コンダクタ２２は、負荷の小さい実行装置４０－ｉを、マイクロデータの転送先として決定する。そして、コンダクタ２２は、転送先の情報をフォワーダ２１へ送信する（ステップＳ３０６）。 When the conductor 22 receives the notification that the data amount of the received microdata exceeds the specified value, the conductor 22 acquires the load status information of each execution device 40-i from the scheduler 23. Further, the conductor 22 determines the execution device 40-i to which the microdata is transferred based on the information on the load status. The conductor 22 determines the execution device 40-i, which has a small load, as the transfer destination of the microdata. Then, the conductor 22 transmits the transfer destination information to the forwarder 21 (step S306).
　コンダクタ２２は、たとえば、図７に示す方法で、マイクロデータの転送先の実行装置４０－ｉを決定する。 The conductor 22 determines the execution device 40-i to which the microdata is transferred, for example, by the method shown in FIG. 7.
　まず、コンダクタ２２は、ジョブが実行されていない実行装置４０－ｉがあるか確認する（ステップＳ４０１）。ジョブが実行されていない実行装置４０－ｉがあれば（ステップＳ４０１でＹＥＳ）、コンダクタ２２は、当該実行装置４０－ｉを、マイクロデータの転送先として決定する（ステップＳ４０２）。ジョブが実行されていない実行装置４０－ｉがない場合（ステップＳ４０１でＮＯ）、コンダクタ２２は、実行装置４０－ｉの空きリソースを確認する。そして、コンダクタ２２は、必要リソース情報が示すリソース量の空きリソースがある実行装置４０－ｉを（ステップＳ４０３でＹＥＳ）、マイクロデータの転送先として決定する（ステップＳ４０４）。必要リソース情報が示すリソース量の空きリソースがある実行装置４０－ｉがなければ（ステップＳ４０３でＮＯ）、コンダクタ２２は、実行装置候補が実行しているジョブの優先度を確認する。そして、コンダクタ２２は、実行装置候補のうち、実行されているジョブの優先度が最も低い実行装置４０－ｉを、マイクロデータの転送先として決定する（ステップＳ４０５）。 First, the conductor 22 confirms whether there is an execution device 40-i in which the job is not executed (step S401). If there is an execution device 40-i in which the job has not been executed (YES in step S401), the conductor 22 determines the execution device 40-i as the transfer destination of the microdata (step S402). If there is no execution device 40-i in which the job has not been executed (NO in step S401), the conductor 22 confirms the free resources of the execution device 40-i. Then, the conductor 22 determines the execution device 40-i (YES in step S403) having free resources of the resource amount indicated by the necessary resource information as the transfer destination of the microdata (step S404). If there is no execution device 40-i having free resources in the amount of resources indicated by the required resource information (NO in step S403), the conductor 22 confirms the priority of the job executed by the execution device candidate. Then, the conductor 22 determines the execution device 40-i having the lowest priority of the job being executed among the execution device candidates as the transfer destination of the microdata (step S405).
　そして、フォワーダ２１は、コンダクタ２２によって決定された転送先の実行装置４０－ｉへ、マイクロデータを送信する（図６のステップＳ３０７）。 Then, the forwarder 21 transmits microdata to the execution device 40-i of the transfer destination determined by the conductor 22 (step S307 in FIG. 6).
　実行装置４０－ｉの受信部４１－ｉは、マイクロデータを受信すると、受信したマイクロデータを、通知手段情報が示す通知手段に書き込み、マイクロデータの受信完了を管理装置２０のフォワーダ２１へ通知する（ステップＳ３０８）。 When the receiving unit 41-i of the executing device 40-i receives the micro data, the received micro data is written in the notification means indicated by the notification means information, and the forwarding completion of the micro data is notified to the forwarder 21 of the management device 20. (Step S308).
　また、フォワーダ２１は、実行装置４０－ｉから、マイクロデータの受信完了が通知された場合、コンダクタ２２へ、データの転送完了を通知する（ステップＳ３０９）。 Further, the forwarder 21 notifies the conductor 22 of the completion of data transfer when the execution device 40-i notifies the completion of reception of microdata (step S309).
　コンダクタ２２は、データの転送完了が通知された場合、実行装置４０－ｉの受信部４１－ｉに、アプリケーションの実行準備ができたことを通知する（ステップＳ３１０）。 When the conductor 22 is notified that the data transfer is completed, the conductor 22 notifies the receiving unit 41-i of the executing device 40-i that the application is ready to be executed (step S310).
　また、受信部４１－ｉは、アプリケーションの実行準備ができたことが管理装置２０から通知された場合、アプリケーションの一時停止を解除する。そして、受信部４１－ｉは、通知手段を介して、アプリケーションの実行開始を実行部４２－ｉへ通知する（ステップＳ３１１）。 Further, when the management device 20 notifies that the receiving unit 41-i is ready to execute the application, the receiving unit 41-i releases the suspension of the application. Then, the receiving unit 41-i notifies the execution unit 42-i of the start of execution of the application via the notification means (step S311).
　実行部４２－ｉは、アプリケーションを実行する。また、実行部４２－ｉは、アプリケーションの実行が終了すると、アプリケーションの終了を受信部４１－ｉへ通知する。 Execution unit 42-i executes the application. Further, when the execution of the application is completed, the execution unit 42-i notifies the reception unit 41-i of the end of the application.
　受信部４１－ｉは、アプリケーションの終了が通知された場合、アプリケーションを一時停止状態にする。 The receiving unit 41-i puts the application in a paused state when the end of the application is notified.
　管理装置２０は、このように動作することによって、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。これにより、管理装置２０は、データを受信する都度アプリケーションを実行させる場合に比べて、実行装置へのデータ転送の回数を減らすことができる。その結果、データの転送時間やファイルシステムへの負荷を低減することができる。また、アプリケーションの実行回数を減らすことができるので、ジョブスケジューラの負荷を低減することができる。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 By operating in this way, the management device 20 transfers the data to the execution device that executes the application when the received data amount of the data related to the predetermined job exceeds the specified value, and the application executes the job. Instruct the execution device. As a result, the management device 20 can reduce the number of times of data transfer to the execution device as compared with the case where the application is executed each time the data is received. As a result, the data transfer time and the load on the file system can be reduced. Moreover, since the number of times the application is executed can be reduced, the load on the job scheduler can be reduced. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　以上で説明したように、本発明の第二の実施形態では、管理装置２０は、所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へデータを転送し、アプリケーションによるジョブの実行を実行装置に指示する。そのため、マイクロデータを用いたジョブを実行する際の負荷低減とスループットの向上をより汎用性が高い方法で実現することが可能になる。 As described above, in the second embodiment of the present invention, the management device 20 transfers data to the execution device that executes the application when the received data amount of the data related to the predetermined job becomes the specified value or more. Transfer and instruct the execution device to execute the job by the application. Therefore, it is possible to reduce the load and improve the throughput when executing a job using microdata by a more versatile method.
　また、本実施形態の実行装置４０－ｉは、管理装置２０から受信したデータを、通知手段情報が示す通知手段に書き込む。これにより、ユーザが希望する通知手段でデータの受け渡しを行うことが可能になる。また、ファイル以外の手段を通知手段とした場合、ファイルシステムへの負荷をより低減することが可能になる。 Further, the execution device 40-i of the present embodiment writes the data received from the management device 20 in the notification means indicated by the notification means information. This makes it possible to transfer data by the notification means desired by the user. Further, when a means other than the file is used as the notification means, the load on the file system can be further reduced.
　［ハードウェア構成例］
　上述した本発明の各実施形態における管理装置（１０、２０）および実行装置４０－ｉ（以下、管理装置等とよぶ）を、一つの情報処理装置（コンピュータ）を用いて実現するハードウェア資源の構成例について説明する。なお、管理装置等は、物理的または機能的に少なくとも二つ以上の複数の情報処理装置が用いられて実現されてもよい。また、管理装置等は、専用の装置として実現されてもよいし、汎用の装置が用いられてもよい。また、管理装置等の一部の機能のみを情報処理装置を用いて実現してもよい。 [Hardware configuration example]
A hardware resource that realizes the management device (10, 20) and the execution device 40-i (hereinafter referred to as a management device, etc.) in each embodiment of the present invention described above by using one information processing device (computer). A configuration example will be described. The management device or the like may be realized by using at least two or more information processing devices physically or functionally. Further, the management device or the like may be realized as a dedicated device, or a general-purpose device may be used. Further, only a part of the functions of the management device and the like may be realized by using the information processing device.
　図８は、本発明の各実施形態の管理装置等を実現可能な情報処理装置のハードウェア構成例を概略的に示す図である。情報処理装置９０は、通信インタフェース９１、入出力インタフェース９２、演算装置９３、記憶装置９４、不揮発性記憶装置９５およびドライブ装置９６を含む。 FIG. 8 is a diagram schematically showing a hardware configuration example of an information processing device that can realize the management device and the like of each embodiment of the present invention. The information processing device 90 includes a communication interface 91, an input / output interface 92, an arithmetic device 93, a storage device 94, a non-volatile storage device 95, and a drive device 96.
　たとえば、図１の転送部１１および指示部１２は、通信インタフェース９１と演算装置９３とで実現することが可能である。 For example, the transfer unit 11 and the instruction unit 12 in FIG. 1 can be realized by the communication interface 91 and the arithmetic unit 93.
　通信インタフェース９１は、各実施形態の管理装置等が、有線および無線のうち少なくとも一方で外部装置と通信するための通信手段である。なお、管理装置等を、少なくとも二つの情報処理装置を用いて実現する場合、それらの装置の間を通信インタフェース９１経由で相互に通信可能なように接続してもよい。 The communication interface 91 is a communication means for the management device or the like of each embodiment to communicate with an external device at least one of wired and wireless. When the management device or the like is realized by using at least two information processing devices, the devices may be connected so as to be able to communicate with each other via the communication interface 91.
　入出力インタフェース９２は、入力デバイスの一例であるキーボードや、出力デバイスとしてのディスプレイ等のマンマシンインタフェースである。 The input / output interface 92 is a man-machine interface such as a keyboard as an example of an input device and a display as an output device.
　演算装置９３は、たとえば、ＣＰＵ（Central Processing Unit）やマイクロプロセッサ等の演算処理装置や複数の電気回路によって実現される。演算装置９３は、たとえば、不揮発性記憶装置９５に記憶された各種プログラムを記憶装置９４に読み出し、読み出したプログラムに従って処理を実行することが可能である。 The arithmetic unit 93 is realized by, for example, an arithmetic processing unit such as a CPU (Central Processing Unit) or a microprocessor, or a plurality of electric circuits. The arithmetic unit 93 can, for example, read various programs stored in the non-volatile storage device 95 into the storage device 94 and execute processing according to the read programs.
　記憶装置９４は、演算装置９３から参照可能な、ＲＡＭ（Random Access Memory）等のメモリ装置であり、プログラムや各種データ等を記憶する。記憶装置９４は、揮発性のメモリ装置であってもよい。 The storage device 94 is a memory device such as a RAM (RandomAccessMemory) that can be referred from the arithmetic unit 93, and stores programs, various data, and the like. The storage device 94 may be a volatile memory device.
　不揮発性記憶装置９５は、たとえば、ＲＯＭ（Read Only Memory）、フラッシュメモリ、等の、不揮発性の記憶装置であり、各種プログラムやデータ等を記憶することが可能である。 The non-volatile storage device 95 is a non-volatile storage device such as a ROM (Read Only Memory), a flash memory, etc., and can store various programs, data, and the like.
　ドライブ装置９６は、たとえば、後述する記録媒体９７に記録されているデータの読み込みやデータの書き込みを処理する装置である。 The drive device 96 is, for example, a device that processes data reading and data writing recorded on a recording medium 97, which will be described later.
　記録媒体９７は、たとえば、光ディスク、光磁気ディスク、半導体フラッシュメモリ等、データを記録可能な任意の記録媒体である。 The recording medium 97 is an arbitrary recording medium capable of recording data, such as an optical disk, a magneto-optical disk, or a semiconductor flash memory.
　本発明の各実施形態は、たとえば、図８に例示した情報処理装置９０により管理装置等を構成し、この管理装置等に対して、上記各実施形態において説明した機能を実現可能なプログラムを供給することにより実現してもよい。 In each embodiment of the present invention, for example, a management device or the like is configured by the information processing device 90 illustrated in FIG. 8, and a program capable of realizing the functions described in each of the above embodiments is supplied to the management device or the like. It may be realized by doing.
　この場合、管理装置等に対して供給したプログラムを、演算装置９３が実行することによって、実施形態を実現することが可能である。また、管理装置等のすべてではなく、一部の機能を情報処理装置９０で構成することも可能である。 In this case, the embodiment can be realized by the arithmetic unit 93 executing the program supplied to the management device or the like. Further, it is also possible to configure some functions of the information processing apparatus 90, not all of the management apparatus and the like.
　さらに、上記プログラムを記録媒体９７に記録しておき、管理装置等の出荷段階、あるいは運用段階等において、適宜上記プログラムが不揮発性記憶装置９５に格納されるよう構成してもよい。なお、この場合、上記プログラムの供給方法は、出荷前の製造段階、あるいは運用段階等において、適当な治具を利用して管理装置等内にインストールする方法を採用してもよい。また、上記プログラムの供給方法は、インターネット等の通信回線を介して外部からダウンロードする方法等の一般的な手順を採用してもよい。 Further, the program may be recorded in the recording medium 97, and the program may be appropriately stored in the non-volatile storage device 95 at the shipping stage, the operation stage, or the like of the management device or the like. In this case, as the supply method of the above program, a method of installing the program in a management device or the like by using an appropriate jig may be adopted at the manufacturing stage before shipment, the operation stage, or the like. Further, as the method of supplying the above program, a general procedure such as a method of downloading from the outside via a communication line such as the Internet may be adopted.
　以上、実施形態を参照して本願発明を説明したが、本願発明は上記実施形態に限定されるものではない。本願発明の構成や詳細には、本願発明のスコープ内で当業者が理解し得る様々な変更をすることができる。 Although the invention of the present application has been described above with reference to the embodiment, the invention of the present application is not limited to the above embodiment. Various changes that can be understood by those skilled in the art can be made within the scope of the present invention in terms of the configuration and details of the present invention.
　上記の実施形態の一部または全部は、以下の付記のようにも記載されうるが、以下には限られない。 A part or all of the above embodiment may be described as in the following appendix, but is not limited to the following.
　　（付記１）
　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送手段と、
　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示手段と
　を備えることを特徴とする管理装置。 (Appendix 1)
A transfer means for transferring the data to an execution device that executes an application when the amount of received data of data related to a predetermined job exceeds a specified value.
A management device including an instruction means for instructing the execution device to execute the job by the application when the transfer of the data is completed.
　　（付記２）
　前記指示手段は、前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
　ことを特徴とする付記１に記載の管理装置。 (Appendix 2)
The management device according to Appendix 1, wherein the instruction means determines the execution device to which the data is transferred based on the load status of the execution device.
　　（付記３）
　前記データは、極小サイズのマイクロデータを含む
　ことを特徴とする付記１または付記２に記載の管理装置。 (Appendix 3)
The management device according to Supplementary Note 1 or 2, wherein the data includes microdata having a very small size.
　　（付記４）
　付記１から付記３のいずれかに記載の管理装置と、
　前記実行装置と
　を備えることを特徴とするシステム。 (Appendix 4)
The management device according to any one of Supplementary Notes 1 to 3 and
A system including the execution device.
　　（付記５）
　前記実行装置は、
　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込む受信手段と、
　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる実行手段と
　を備えることを特徴とする付記４に記載のシステム。 (Appendix 5)
The execution device is
A receiving means that receives notification means information indicating the type of the interface to which the data is written and writes the received data to the interface of the type indicated by the notification means information.
The system according to Appendix 4, further comprising an execution means for causing the application to execute the job by using the data written in the interface when the execution instruction of the application is received.
　　（付記６）
　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
　ことを特徴とする付記５に記載のシステム。 (Appendix 6)
The system according to Appendix 5, wherein the interface type is one of a file, a named pipe, and a shared memory.
　　（付記７）
　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送し、
　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する
　ことを特徴とする管理方法。 (Appendix 7)
When the amount of data received for a given job exceeds the specified value, the data is transferred to the execution device that executes the application.
A management method comprising instructing the execution device to execute the job by the application when the transfer of the data is completed.
　　（付記８）
　前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
　ことを特徴とする付記７に記載の管理方法。 (Appendix 8)
The management method according to Appendix 7, wherein the execution device to which the data is transferred is determined based on the load status of the execution device.
　　（付記９）
　前記データは、極小サイズのマイクロデータを含む
　ことを特徴とする付記７または付記８に記載の管理方法。 (Appendix 9)
The management method according to Appendix 7 or Appendix 8, wherein the data includes microdata having a very small size.
　　（付記１０）
　前記実行装置は、
　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込み、
　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる
　をことを特徴とする付記９に記載の管理方法。 (Appendix 10)
The execution device is
The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
The management method according to Appendix 9, wherein when the application execution instruction is received, the application is made to execute the job by using the data written in the interface.
　　（付記１１）
　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
　ことを特徴とする付記１０に記載の管理方法。 (Appendix 11)
The management method according to Appendix 10, wherein the interface type is one of a file, a named pipe, and a shared memory.
　　（付記１２）
　コンピュータに、
　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送機能と、
　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示機能と
　を実行させることを特徴とする管理プログラムを記録したコンピュータ読み取り可能な記録媒体。 (Appendix 12)
On the computer
A transfer function that transfers the data to the execution device that executes the application when the amount of data received for a predetermined job exceeds the specified value.
A computer-readable recording medium recording a management program, characterized in that when the transfer of data is completed, an instruction function for instructing the execution device to execute the job by the application is executed.
　　（付記１３）
　前記指示機能は、前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
　ことを特徴とする付記１２に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。 (Appendix 13)
The instruction function is a computer-readable recording medium recording a management program according to Appendix 12, characterized in that the execution device to which the data is transferred is determined based on the load status of the execution device.
　　（付記１４）
　前記データは、極小サイズのマイクロデータを含む
　ことを特徴とする付記１２または付記１３に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。 (Appendix 14)
The data is a computer-readable recording medium on which the management program according to Appendix 12 or Appendix 13, characterized in that it contains microdata of very small size, is recorded.
　　（付記１５）
　前記実行装置は、
　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込み、
　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる
　をことを特徴とする付記１４に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。 (Appendix 15)
The execution device is
The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
When the execution instruction of the application is received, the computer can read the management program according to the appendix 14, characterized in that the application is made to execute the job by using the data written in the interface. Recording medium.
　　（付記１６）
　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
　ことを特徴とする付記１５に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。 (Appendix 16)
A computer-readable recording medium recording the management program according to Appendix 15, wherein the interface type is one of a file, a named pipe, and a shared memory.
　この出願は、２０２０年１１月２７日に出願された日本出願特願２０２０－１９６７７９を基礎とする優先権を主張し、その開示の全てをここに取り込む。 This application claims priority on the basis of Japanese Application Japanese Patent Application No. 2020-196779 filed on November 27, 2020, and incorporates all of its disclosures herein.
　１０、２０　　管理装置
　１１　　転送部
　１２　　指示部
　２１　　フォワーダ
　２２　　コンダクタ
　２３　　スケジューラ
　４０－ｉ　　実行装置
　４１－ｉ　　受信部
　４２－ｉ　　実行部
　６０　　利用者端末
　９０　　情報処理装置
　９１　　通信インタフェース
　９２　　入出力インタフェース
　９３　　演算装置
　９４　　記憶装置
　９５　　不揮発性記憶装置
　９６　　ドライブ装置
　９７　　記録媒体 10, 20 Management device 11 Transfer section 12 Indicator section 21 Forwarder 22 Conductor 23 Scheduler 40-i Execution device 41-i Receiver section 42-i Execution section 60 User terminal 90 Information processing device 91 Communication interface 92 Input / output interface 93 Computing device 94 Storage device 95 Non-volatile storage device 96 Drive device 97 Recording medium

Claims (16)

  1. 　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送手段と、
    　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示手段と
    　を備えることを特徴とする管理装置。     A transfer means for transferring the data to an execution device that executes an application when the amount of received data of data related to a predetermined job exceeds a specified value.
    A management device including an instruction means for instructing the execution device to execute the job by the application when the transfer of the data is completed.
  2. 　前記指示手段は、前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
    　ことを特徴とする請求項１に記載の管理装置。     The management device according to claim 1, wherein the instruction means determines the execution device to which the data is transferred based on the load status of the execution device.
  3. 　前記データは、極小サイズのマイクロデータを含む
    　ことを特徴とする請求項１または請求項２に記載の管理装置。     The management device according to claim 1 or 2, wherein the data includes microdata having a very small size.
  4. 　請求項１から請求項３のいずれかに記載の管理装置と、
    　前記実行装置と
    　を備えることを特徴とするシステム。     The management device according to any one of claims 1 to 3,
    A system including the execution device.
  5. 　前記実行装置は、
    　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込む受信手段と、
    　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる実行手段と
    　を備えることを特徴とする請求項４に記載のシステム。     The execution device is
    A receiving means that receives notification means information indicating the type of the interface to which the data is written and writes the received data to the interface of the type indicated by the notification means information.
    The system according to claim 4, further comprising an execution means for causing the application to execute the job by using the data written in the interface when the execution instruction of the application is received.
  6. 　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
    　ことを特徴とする請求項５に記載のシステム。     The system according to claim 5, wherein the interface type is one of a file, a named pipe, and a shared memory.
  7. 　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送し、
    　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する
    　ことを特徴とする管理方法。     When the amount of data received for a given job exceeds the specified value, the data is transferred to the execution device that executes the application.
    A management method comprising instructing the execution device to execute the job by the application when the transfer of the data is completed.
  8. 　前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
    　ことを特徴とする請求項７に記載の管理方法。     The management method according to claim 7, wherein the executing device to which the data is transferred is determined based on the load status of the executing device.
  9. 　前記データは、極小サイズのマイクロデータを含む
    　ことを特徴とする請求項７または請求項８に記載の管理方法。     The management method according to claim 7, wherein the data includes microdata having a very small size.
  10. 　前記実行装置は、
    　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込み、
    　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる
    　をことを特徴とする請求項９に記載の管理方法。     The execution device is
    The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
    The management method according to claim 9, wherein when the application execution instruction is received, the application is made to execute the job by using the data written in the interface.
  11. 　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
    　ことを特徴とする請求項１０に記載の管理方法。     The management method according to claim 10, wherein the type of the interface is any of a file, a named pipe, and a shared memory.
  12. 　コンピュータに、
    　所定のジョブに関するデータの受信データ量が指定値以上となった場合に、アプリケーションを実行する実行装置へ前記データを転送する転送機能と、
    　前記データの転送が完了した場合に、前記アプリケーションによる前記ジョブの実行を前記実行装置に指示する指示機能と
    　を実行させることを特徴とする管理プログラムを記録したコンピュータ読み取り可能な記録媒体。     On the computer
    A transfer function that transfers the data to the execution device that executes the application when the amount of data received for a predetermined job exceeds the specified value.
    A computer-readable recording medium recording a management program, characterized in that when the transfer of data is completed, an instruction function for instructing the execution device to execute the job by the application is executed.
  13. 　前記指示機能は、前記実行装置の負荷状況に基づいて、前記データの転送先の前記実行装置を決定する
    　ことを特徴とする請求項１２に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。     The computer-readable recording medium on which the management program according to claim 12, wherein the instruction function determines the execution device to which the data is transferred based on the load status of the execution device.
  14. 　前記データは、極小サイズのマイクロデータを含む
    　ことを特徴とする請求項１２または請求項１３に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。     A computer-readable recording medium on which the management program according to claim 12 or 13, characterized in that the data includes microdata of very small size, is recorded.
  15. 　前記実行装置は、
    　前記データの書き込み先のインタフェースの種別を示す通知手段情報を受信し、前記通知手段情報が示す種別のインタフェースに、受信した前記データを書き込み、
    　前記アプリケーションの実行指示を受信した場合に、前記インタフェースに書き込まれた前記データを用いて、前記アプリケーションに前記ジョブを実行させる
    　をことを特徴とする請求項１４に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。     The execution device is
    The notification means information indicating the type of the interface to which the data is written is received, and the received data is written to the interface of the type indicated by the notification means information.
    A computer reading that records the management program according to claim 14, wherein when the application execution instruction is received, the application is made to execute the job by using the data written in the interface. Possible recording medium.
  16. 　前記インタフェースの種別は、ファイル、名前付きパイプおよび共有メモリのいずれかである
    　ことを特徴とする請求項１５に記載の管理プログラムを記録したコンピュータ読み取り可能な記録媒体。     A computer-readable recording medium recording the management program according to claim 15, wherein the interface type is one of a file, a named pipe, and a shared memory.
PCT/JP2021/038769 2020-11-27 2021-10-20 Management device, system, management method, and recording medium WO2022113578A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
DE112021006183.6T DE112021006183T5 (en) 2020-11-27 2021-10-20 MANAGEMENT APPARATUS, SYSTEM, MANAGEMENT METHOD AND MANAGEMENT PROGRAM
JP2022565115A JPWO2022113578A5 (en) 2021-10-20 Management device, system, management method and management program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-196779 2020-11-27
JP2020196779 2020-11-27

Publications (1)

Publication Number Publication Date
WO2022113578A1 true WO2022113578A1 (en) 2022-06-02

Family

ID=81754263

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/038769 WO2022113578A1 (en) 2020-11-27 2021-10-20 Management device, system, management method, and recording medium

Country Status (2)

Country Link
DE (1) DE112021006183T5 (en)
WO (1) WO2022113578A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017199807A1 (en) * 2016-05-19 2017-11-23 日本電信電話株式会社 Sensor relay device and sensor relay system
WO2018002976A1 (en) * 2016-06-27 2018-01-04 株式会社日立製作所 Management device, execution environment setting method, stream data processing system
US20190213509A1 (en) * 2018-01-10 2019-07-11 Walmart Apollo, Llc System for relational-impact based task management

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7885969B2 (en) 2007-09-17 2011-02-08 International Business Machines Corporation System and method for executing compute-intensive database user-defined programs on an attached high-performance parallel computer
US10514952B2 (en) 2016-09-15 2019-12-24 Oracle International Corporation Processing timestamps and heartbeat events for automatic time progression
JP7392292B2 (en) 2019-05-31 2023-12-06 ブラザー工業株式会社 Water-based ink for inkjet recording

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017199807A1 (en) * 2016-05-19 2017-11-23 日本電信電話株式会社 Sensor relay device and sensor relay system
WO2018002976A1 (en) * 2016-06-27 2018-01-04 株式会社日立製作所 Management device, execution environment setting method, stream data processing system
US20190213509A1 (en) * 2018-01-10 2019-07-11 Walmart Apollo, Llc System for relational-impact based task management

Also Published As

Publication number Publication date
DE112021006183T5 (en) 2023-09-28
JPWO2022113578A1 (en) 2022-06-02

Similar Documents

Publication Publication Date Title
JP5022030B2 (en) Computer system, server constituting the same, job execution control method thereof, and program
JP2007041720A (en) Job step execution program and job step execution method
US8280197B1 (en) Managed background loading of image resources in resource-constrained devices
JP6406027B2 (en) Information processing system, information processing apparatus, and memory access control method
US8775767B2 (en) Method and system for allocating memory to a pipeline
WO2022113578A1 (en) Management device, system, management method, and recording medium
WO2024103927A1 (en) Job scheduling method and apparatus in hybrid deployment scenario, and electronic device
JP5294014B2 (en) File sharing method, computer system, and job scheduler
WO2011070716A1 (en) Information processing system, control method, and non-transitory computer readable medium storing program
US8359564B2 (en) Circuit design information generating equipment, function execution system, and memory medium storing program
JP4140014B2 (en) Client server system and data processing method of client server system
US12056393B2 (en) System and method for exchanging messages
JP4170330B2 (en) Information processing device
JP2014229301A (en) Smart terminal fuzzing apparatus and method using multi-node
JP2015094976A (en) Information processing apparatus, information processing method, and program
JP2005258509A (en) Storage device
CN112748883A (en) IO request pipeline processing device, method, system and storage medium
WO2022074858A1 (en) Memory control device and control method
JP7080698B2 (en) Information processing equipment
JP2007018195A (en) Information processing method and information processor
JP6115253B2 (en) Print system, spool server, spool method, and program
JP4877526B2 (en) Client server system and data processing method of client server system
WO2020090009A1 (en) Arithmetic processing device and control method thereof
JP2019159722A (en) Information processing device, arithmetic processing device, and control method for information processing device
JP6126259B1 (en) Monitoring device, monitoring method, and program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21897556

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202317029518

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2022565115

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 112021006183

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21897556

Country of ref document: EP

Kind code of ref document: A1