A computing network includes nodes of different work groups. Nodes of a work group are dedicated to transactions of the work group. If a node of a first work group is predicted to have an idleness window, a second work group may borrow the node to execute a transaction of the second work group. At least a subset of steps of the transaction may be categorized into a step group. Trees of a transaction may be categorized into one or more tree groups. A node is selected for executing a transaction, if the predicted idleness duration of the node is sufficient relative to the predicted runtime of the transaction, the step group, and/or tree group. A credit system is maintained. A first work group transfers a credit to a second work group when borrowing a node of the second work group for executing a transaction of the first work group.

The present disclosure relates to a method, a device, and a program product for managing multiple computing tasks on a batch basis. A method includes: identifying a task type of the multiple computing tasks in response to receiving a request to use a computing unit in a computing system to perform the multiple computing tasks; acquiring a scheduling time overhead incurred for scheduling the multiple computing tasks for execution by the computing unit; determining, based on the task type and the scheduling time overhead, a batch size for dividing the multiple computing tasks; and dividing the multiple computing tasks into at least one batch based on the batch size. A corresponding device and a corresponding computer program product are provided. With the example implementations of the present disclosure, the batch size for dividing multiple computing tasks can be dynamically determined, so that the performance of the computing system can meet user demands.

A database management system for controlling prioritized transactions, comprising: a processor adapted to: receive from a client module a request to write into a database item as part of a high-priority transaction; check a lock status and an injection status of the database item; when the lock status of the database item includes a lock owned by a low-priority transaction and the injection status is not-injected status: change the injection status of the database item to injected status; copy current content of the database item to an undo buffer of the low-priority transaction; and write into a storage engine of the database item.

Provided is an apparatus for managing user authentication in a blockchain network and the apparatus comprises a processor configured to transmit, to a server, a request for a snapshot identifier (ID) with user data comprising at least one of one-time password, biometric data, context data, routine data, or device metadata, receive the snapshot ID generated based on the user data, initiate a transaction with the snapshot ID in the blockchain network comprising a blockchain server which authenticates the snapshot ID, and output blockchain transaction data associated with the transaction based on the authentication of the snapshot ID.

Simulator includes a first core unit corresponding to the first simulation model, a second core unit corresponding to the second simulation model, a slave block unit for communicating with one of the first core unit and the second core unit, the first core unit and the second core unit and a simulation control unit for causing either to execute instructions. The first core unit includes a high-speed mode instruction execution control unit that stops executing subsequent instructions in response to a request for switching from the first simulation model to the second simulation model, and a transaction monitor unit that monitors whether or not the transaction processing between the first core unit and the slave block unit has been completed. The simulation control unit causes the second core unit to execute instructions in response to a notification of completion of the transaction processing from the transaction monitor unit.

A method comprises collecting data corresponding to a plurality of components in a system, wherein the data comprises information about at least one of respective protocols and respective interfaces associated with respective ones of the plurality of components. The data is analyzed to determine at least one of the respective protocols and the respective interfaces associated with the respective ones of the plurality of components. In the method, operations of one or more components of the plurality of components are tested based at least in part on the determination of the at least one of the respective protocols and the respective interfaces. The method further includes outputting respective statuses of the one or more components, wherein the respective statuses are derived at least in part from the testing.

A method for managing transaction is performed in a blockchain-based computing system and includes receiving a request for processing a first individual transaction from a client terminal, generating a batch transaction by aggregating a plurality of individual transactions including the first individual transaction, processing the generated batch transaction via a blockchain network, such that a status record associated with the batch transaction is recorded in the blockchain, and providing the client terminal with an identifier of the batch transaction and index information on the first individual transaction, wherein the status record associated with the batch transaction includes a first status record associated with the first individual transaction, and wherein the index information on the first individual transaction is determined based on a location of the first status record in the status record.

Aspects of the disclosure relate to a machine-learning transaction-prediction engine for seasoning an anticipated manual transaction. The transaction may occur in a transaction session. The seasoning may occur prior to execution of the anticipated manual transaction. The transaction-prediction engine may include a receiving/storage module configured to receive and store identification information of the transactor. The engine may also include a step-retrieval module configured to retrieve a set of in-session transaction steps associated with the transactor. In addition, the engine may include a history-retrieval module configured to retrieve, based on the stored identification information, historical transactional information associated with the transactor. The historical transaction information comprising a plurality of historical transaction patterns associated with the transactor. The engine may also include a processor module configured to initiate the anticipated manual transaction by predicting and provisionally completing the in-session transaction steps. The predicting may be based on the set of in-session transaction associated with the transactor and on the plurality of historical patterns.

Techniques are disclosed relating to determining a predicted time interval for querying a database beginning at a starting point in time to retrieve a specified number of records. A computer system receives a request for records from a database that stores timestamped records, where the request is for a specified number of records beginning at a starting point in time. The computer system then determines a predicted time interval for querying the database beginning at the starting point in time to retrieve the specified number of records, where the predicted time interval may be determined by a machine learning module that is trained using historical database transaction data. Such techniques may advantageously improve the efficiency of individual queries in fetching a desired amount of data from a database for applications.

An arrangement includes a plurality of clusters and an interface through which a distributed federation database is accessible, wherein each of the clusters includes a cluster interface; a cluster local memory configured to store local cluster resources; and a federation controller. The federation controller is configured to: receive a first notification from the distributed federation database, wherein the first notification indicates a change relating to a federation resource in the distributed federation database; analyze the first notification; modify the local resource based on the analysis; and update a status of the federation resource in the distributed federation database when the local resource has been stored.