Provided are a message interaction processing method and device. The method includes: a first buffer with a preset size is applied for to a Central Processing Unit (CPU) and/or a chip; and message interaction is performed between the CPU and the chip through the first buffer, wherein the first buffer is used for storing at least two messages. By the disclosure, the problem that frequent switching between states may cause high resource overhead and low message transmission efficiency under the condition of large message interaction between the CPU and the chip is solved, and the effect of remarkably improving message sending and receiving efficiency and performance of network equipment is further achieved.

Recent techniques for workload characterization of an application to be executed in a serverless execution environment or cloud are based on benchmark-approximation. Multiple microbenchmarks are run against the multiple VM configurations and a score is calculated which is used for mapping futuristic workloads to the appropriate configuration. Embodiments herein disclose method and system for workload characterization-based capacity planning of an actual application running on-premise with different configurations of the same machine and providing a cost-effective and high-performance serverless execution environment. Resource demand of each API in the application workflow is evaluated. Based on the resource demand of each API, a mapping is performed to the serverless platform on cloud. Additionally, characterization of threads within each API is performed and each thread is mapped to a serverless instance based on its resource requirements.

Apparatuses, systems, and techniques to perform an API to retrieve a portion of an image based, at least in part, on an indication of the portion of said image. In at least one embodiment, an API uses a handle that references a memory location for said image, and said image has a first plane corresponding to image data (e.g., color) and a second plane corresponding to different image data (e.g., intensity). Apparatuses, systems, and techniques to perform an API to retrieve a portion of an image based, at least in part, on an indication of the portion of the image.

Apparatuses, systems, and techniques to perform one or more APIs to receive, update, wait on, and invalidate one or more timeline semaphores. In at least one embodiment, apparatuses, systems, and techniques to manage computing resources (e.g., streams for a workload) can reference, use, and read a count value corresponding to a timeline semaphore. In at least one embodiment, APIs can communicate with drivers or libraries to interact with a handle of a timeline semaphore.

A method includes creating a publisher configured to send messages over a channel having a shared memory. The method includes creating at least one subscriber configured to receive the messages over the channel by sequentially referencing memory slots of the plurality of memory slots. The method includes determining that the next sequential memory slot is currently referenced by a subscriber. The method includes delaying sending the message by the publisher based on determining that the next sequential memory slot is currently referenced by the subscriber. The method includes receiving an event trigger indicative of message reading by the subscriber. The method includes, responsive to receiving the event trigger, determining that the next sequential memory slot is not currently referenced. The method includes sending the message to the next sequential memory slot based on determining that the next sequential memory slot is not currently referenced.

Apparatuses, systems, and techniques to perform an API to retrieve a portion of an image based, at least in part, on an indication of the portion of said image. In at least one embodiment, an API uses a handle that references a memory location for said image, and said image has a first plane corresponding to image data (e.g., color) and a second plane corresponding to different image data (e.g., intensity). Apparatuses, systems, and techniques to perform an API to retrieve a portion of an image based, at least in part, on an indication of the portion of the image.

In some examples, a system partitions a shared memory address space of a shared memory among a plurality of processing entities into a plurality of memory partitions, where a respective memory partition is associated with a respective processing entity. A first processing entity forwards, to a second processing entity, a first data operation, based on a determination by the first processing entity that the first data operation is to be applied to data for a memory partition associated with the second processing entity. The second processing entity applies the first data operation that includes writing data of the first data operation to the memory partition associated with the second processing entity using a non-atomic operation.

Apparatuses, systems, and techniques to perform one or more APIs to receive, update, wait on, and invalidate one or more timeline semaphores. In at least one embodiment, apparatuses, systems, and techniques to manage computing resources (e.g., streams for a workload) can reference, use, and read a count value corresponding to a timeline semaphore. In at least one embodiment, APIs can communicate with drivers or libraries to interact with a handle of a timeline semaphore.

Disclosed herein are system, method, and computer program product embodiments for microservice load balancing and distribution using an embedded computer capacity module. An embodiment operates by retrieving an application programming interface (API) request from a client. The embodiment stores objects representing the API request in a job detail database containing details related to the API request. The embodiment determines an available bandwidth of the service instance. The embodiment transmits the determined available bandwidth of the service instance to a job processor. The embodiment selects tasks from the objects representing the API request stored in the job detail database based on the determined available bandwidth of the service instance. The embodiment executes the selected tasks.

Devices and techniques for pipeline merging in a circuit are described herein. A parallel pipeline result can be obtained for a transaction index of a parallel pipeline. Here, the parallel pipeline is one of several parallel pipelines that share transaction indices. An element in a vector can be marked. The element corresponds to the transaction index. The vector is one of several vectors respectively assigned to the several parallel pipelines. Further each element in the several vectors corresponds to a possible transaction index with respective elements between vectors corresponding to the same transaction index. Elements between the several vectors that correspond to the same transaction index can be compared to determine when a transaction is complete. In response to the transaction being complete, the result can be released to an output buffer in response to the transaction being complete.