WO2022113578A1 - Dispositif de gestion, système, procédé de gestion et support d'enregistrement - Google Patents

Dispositif de gestion, système, procédé de gestion et support d'enregistrement 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
English (en)
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/de
Priority to JP2022565115A priority patent/JPWO2022113578A5/ja
Publication of WO2022113578A1 publication Critical patent/WO2022113578A1/fr

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

Afin de permettre la réduction des charges et l'amélioration du débit lors de l'exécution de tâches dans lesquelles des micro-données sont utilisées pour être réalisées par un procédé plus polyvalent, ce dispositif de gestion est caractérisé en ce qu'il comprend : une unité de transfert qui, lorsque la quantité de données reçues concernant une tâche prescrite devient supérieure ou égale à une valeur désignée, transfère les données à un dispositif d'exécution qui exécute une application ; et une unité d'instruction qui, lorsque le transfert des données est achevé, ordonne au dispositif d'exécution d'exécuter la tâche par l'application.
PCT/JP2021/038769 2020-11-27 2021-10-20 Dispositif de gestion, système, procédé de gestion et support d'enregistrement WO2022113578A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
DE112021006183.6T DE112021006183T5 (de) 2020-11-27 2021-10-20 Management-vorrichtung, system, management-verfahren und management-programm
JP2022565115A JPWO2022113578A5 (ja) 2021-10-20 管理装置、システム、管理方法および管理プログラム

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 (fr) 2022-06-02

Family

ID=81754263

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/038769 WO2022113578A1 (fr) 2020-11-27 2021-10-20 Dispositif de gestion, système, procédé de gestion et support d'enregistrement

Country Status (2)

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

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017199807A1 (fr) * 2016-05-19 2017-11-23 日本電信電話株式会社 Dispositif de relais de capteur et système de relais de capteur
WO2018002976A1 (fr) * 2016-06-27 2018-01-04 株式会社日立製作所 Dispositif de gestion, procédé de réglage d'environnement d'exécution, système de traitement de données de flux
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 (ja) 2019-05-31 2023-12-06 ブラザー工業株式会社 インクジェット記録用水性インク

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017199807A1 (fr) * 2016-05-19 2017-11-23 日本電信電話株式会社 Dispositif de relais de capteur et système de relais de capteur
WO2018002976A1 (fr) * 2016-06-27 2018-01-04 株式会社日立製作所 Dispositif de gestion, procédé de réglage d'environnement d'exécution, système de traitement de données de flux
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 (de) 2023-09-28
JPWO2022113578A1 (fr) 2022-06-02

Similar Documents

Publication Publication Date Title
JP5022030B2 (ja) コンピュータシステム、これを構成するサーバ、そのジョブ実行制御方法及びプログラム
JP2007041720A (ja) ジョブステップ実行プログラムおよびジョブステップ実行方法
US8280197B1 (en) Managed background loading of image resources in resource-constrained devices
JP6406027B2 (ja) 情報処理システム、情報処理装置、メモリアクセス制御方法
US8775767B2 (en) Method and system for allocating memory to a pipeline
WO2022113578A1 (fr) Dispositif de gestion, système, procédé de gestion et support d'enregistrement
WO2024103927A1 (fr) Procédé et appareil de planification de tâche dans un scénario de déploiement hybride, et dispositif électronique
JP5294014B2 (ja) ファイル共有方法、計算機システム及びジョブスケジューラ
WO2011070716A1 (fr) Systeme de traitement d'informations, procede de commande, et programme de stockage de support lisible par ordinateur non transitoire
US8359564B2 (en) Circuit design information generating equipment, function execution system, and memory medium storing program
JP4140014B2 (ja) クライアントサーバシステムおよびクライアントサーバシステムのデータ処理方法
US12056393B2 (en) System and method for exchanging messages
JP4170330B2 (ja) 情報処理装置
JP2014229301A (ja) マルチノードを用いるスマート端末ファジング装置およびその方法
JP2015094976A (ja) 情報処理装置、情報処理方法、及び、プログラム
JP2005258509A (ja) ストレージ装置
CN112748883A (zh) 一种io请求流水线处理设备、方法、系统及存储介质
WO2022074858A1 (fr) Dispositif de commande de mémoire et procédé de commande
JP7080698B2 (ja) 情報処理装置
JP2007018195A (ja) 情報処理方法および情報処理装置
JP6115253B2 (ja) プリントシステム、スプールサーバ、スプール方法、及びプログラム
JP4877526B2 (ja) クライアントサーバシステムおよびクライアントサーバシステムのデータ処理方法
WO2020090009A1 (fr) Dispositif de traitement arithmétique et son procédé de commande
JP2019159722A (ja) 情報処理装置、演算処理装置及び情報処理装置の制御方法
JP6126259B1 (ja) 監視装置、監視方法、及びプログラム

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