Data are maintained in a distributed computing system that describe a graph. The graph represents relationships among items. The graph has a plurality of vertices that represent the items and a plurality of edges connecting the plurality of vertices. At least one vertex of the plurality of vertices includes a set of label values indicating the at least one vertex's strength of association with a label from a set of labels. The set of labels describe possible characteristics of an item represented by the at least one vertex. At least one edge of the plurality of edges includes a set of label weights for influencing label values that traverse the at least one edge. A label propagation algorithm is executed for a plurality of the vertices in the graph in parallel for a series of synchronized iterations to propagate labels through the graph.

A coarse-grained reconfigurable (CGR) processor comprises a first network and a second network; a plurality of agents coupled to the first network; an array of CGR units coupled together by the second network; and a tile agent coupled between the first network and the second network. The tile agent further comprises a plurality of links; a plurality of credit counters associated with respective agents of the plurality of agents; a plurality of credit-hog counters associated with respective links of the plurality of links. The tile agent further comprises an arbiter to manage access to the first network from the plurality of links based their associated credit-hog counters; wherein a credit-hog counter of the plurality of credit-hog counters changes in response to processing a request for a transaction from its associated link.

A system is presented that includes a communication link, a runtime processor coupled to the communication link, and a reconfigurable processor. The reconfigurable processor is adapted for generating an interrupt to the runtime processor in response to a predetermined event and includes multiple arrays of coarse-grained reconfigurable (CGR) units and an interface to the communication link that couples the reconfigurable processor to the runtime processor via the communication link. The runtime processor is adapted for configuring the interface to the communication link to provide access to the multiple arrays of coarse-grained reconfigurable units from a physical function driver and from at least one virtual function driver, and the reconfigurable processor is adapted for sending the interrupt to the physical function driver and to a virtual function driver of the at least one virtual function driver within the runtime processor.

Disclosed herein are system, method, and computer program product embodiments for implementing automatic taxonomy tags in an API microgateway. The API microgateway may receive a plurality of API requests for an API managed by a customer in a period of time and route the plurality of API request to an instance of the API according to a policy of the API. The API microgateway may aggregate metrics information related to the plurality of API requests. The aggregated metrics information may include request features, response features, policy features, and performance features. In response to a cluster of the metrics information corresponding to a tag in a tag prediction system, the aggregated metrics information may be labeled with the tag. The tag and the aggregated metrics information may be added to an access log and sent to the customer.

A method and a related apparatus for implementing a batch system call are disclosed. The method includes: loading an executable program to a user-mode virtual address space, where the executable program is obtained by compiling source code of the batch system call, and includes abstract syntax tree (AST) data of the batch system call; and invoking a first instruction to invoke a kernel to generate, based on the AST data in the user-mode virtual address space, binary code that is used to implement the batch system call. Because there is difficulty in inserting malicious data into a data structure like the AST, it is difficult to insert malicious code into the binary code of the batch system call, so as to avoid an error or an excessively long delay caused by the malicious code when the kernel runs the binary code of the batch system call, thereby improving security of the batch system call.

Disclosed herein are system, method, and computer program product embodiments for implementing statistical distributed rate limiting in an Application Programming Interfaces (API) Gateway cluster. An API Gateway cluster may comprise a plurality of gateway nodes and manage API traffic to ensure proper function and protect the health of an API. Each gateway node may use a distributed rate limiting algorithm based on the physics formulas for average velocity, average acceleration and distance based on time determine the total number of API requests accepted by all the nodes in the cluster. Implementation of statistical distributed rate limiting allows for accurate estimations of the total requests accepted by cluster without requiring each node to share its status with the other nodes in the cluster upon receiving each API request. This approach allows for minimum computational overhead while prioritizing the health of the API.

Disclosed herein are system, method, and computer program product embodiments for providing a streamlines API development environment. In the environment, pre-coded code modules corresponding to common policy functions are stored in memory and can be used, copied, and/or incorporated into developer custom policies. Function calls and/or references to specific code modules can be incorporated into developer custom policies, which will invoke one of the stored code modules. Additionally, one or more compilers are provided to compile code from a development language to a predetermined production language. Although the development language is preset by the development environment, other languages can be supported by downloading compilers for preferred development languages.

The examples described herein extend application lifecycle management (ALM) processes (e.g., create, update, delete, retrieve, import, export, uninstall, publish) to user-created application platform components. First and second components are generated within an application platform. The first component is customized at least by indicating whether the first component is subject to localization, defining a layering of the first component, and indicating whether the first component is protected from downstream modification. The second component is customized in accordance with customizing the first component, and is further customized by defining a dependency of the second component on the first component. The components are deployed in a target environment with metadata representing the customizations and enabling the ALM processes.

Managing per-thread stop-the-world garbage collection is provided. A set of threads of a plurality of threads is transitioned from a normal thread state to a no-read-no-write thread state at a first safepoint of a pair of contiguous safepoints using a first set of thread transition code inserted in program code of an application at the first safepoint. Execution of any remaining threads of the plurality of threads having a normal thread state is suspended at the first safepoint. Stop-the-world garbage collection of a memory heap dedicated to the application is performed while allowing the set of threads of the plurality of threads having the no-read-no-write thread state to continue execution in a region within the program code between the pair of contiguous safepoints based on a special status tag of the first safepoint of the pair of contiguous safepoints.

A system is presented that includes a communication link, a runtime processor, and a reconfigurable processor. The reconfigurable processor is adapted for generating an interrupt to the runtime processor in response to a predetermined event and includes first and second dies arranged in a package, having respective first and second arrays of coarse-grained reconfigurable (CGR) units, and respective first and second communication link interfaces coupled to the communication link. The runtime processor is adapted for configuring the first and second communication link interfaces to provide access to the first and second arrays of coarse-grained reconfigurable units from first and second physical function drivers and from at least one virtual function driver, and the reconfigurable processor is adapted for sending the interrupt to the first or to the second physical function driver and for sending the interrupt to a virtual function driver of the at least one virtual function driver.