International Business Machines Corporation

Kyndryl, Inc.

Samir Nasser

Kyle Gene Brown

Jeremy R Fox

Brian M O'Connell

Kulvir Singh Bhogal

Shikhar Kwatra

Zachary A Silverstein

Ann Corrao

Peter C Bahrs

Neil Delima

Brian M O'connell

Methods, computer program products, and systems are presented. The method computer program products, and systems can include, for instance: marking of a request to define a marked request that includes associated metadata, wherein the metadata specifies action for performing by a resource interface associated to a production environment resource of a production environment, wherein the resource interface is configured for emulating functionality of the production environment resource; and sending the marked request to the resource interface for performance of the action specified by the metadata.

Production software application performance and resiliency testing

Methods, computer program products, and systems are presented. The method computer program products, and systems can include, for instance: predicting, with use of one or more predictive model, subsequent future state data of a computing node having an associated working memory, wherein the subsequent future state data specifies that a certain transaction currently uninvoked will be invoked by the computing node; prior to the invoking of the certain transaction, proactively establishing one or more control parameter value for controlling the working memory in dependence on the future state data; invoking the certain transaction in response to receipt, by the computing node, of transaction invoking request data for invoking the certain transaction; and executing the certain transaction in dependence on at least one control parameter value of the one or more control parameter value for controlling the working memory.

Working memory management

A computer-implemented method groups queries to reduce performance degradation. The method includes, receiving, by a database manager, a set of queries from one or more requestors, wherein each query of the set of queries includes an access plan. The method includes, determining, based at least on the access plan of each query, that a first query in the set of queries is incompatible with a second query of the set of queries. The method includes, grouping, in response to the first query and the second query being incompatible, the first query in a first group, and the second query in a second group, wherein the first group and the second group are included in a set of groups. The method includes, determining an order for each group of the set of groups. The method further includes, executing, in response to determining the order, each group in the determined order.

Prioritization and optimization of database workloads

Information is gathered on microservice interactions. Two or more microservice failures are detected. For each microservices failure, a microservice restoration time is determined. An expected total cost of a downtime for each microservice is determined. Based on the determined expected total cost of the downtime for each microservice, an order of microservices to restore is determined.

Prioritization of service restoration in microservices architecture

In filtering requests to be forwarded to a runtime environment, a filtering apparatus intercepts a new runtime request for the runtime environment and determines execution paths that may be traversed by the runtime request when executed in the runtime environment. The filtering apparatus assigns a probability of traversal by the runtime request to each of the execution paths and identifies at least one given execution path that reference a stressed resource of the runtime environment. Based on the probabilities assigned to the at least one given execution path, the filtering apparatus determines whether or not to block the runtime request from being sent to the runtime environment. If the probability assigned to the at least one given execution path exceeds a configured threshold, the runtime request is blocked from being sent to the runtime environment. Otherwise, the runtime request is sent to the runtime environment.

Software request-filtering predictive technique based on resource usage probabilities

A method addresses a defect in software. The method periodically captures snapshots of versions of code for a particular software program as one or more functionalities are added to the particular software program. The method determines that a current version of the particular software program has a defect, and then iteratively tests previous versions of that particular software program until a most-recent non-defective version of the particular software program is detected. A software developer is directed to either debug the current version of the particular software program, or else re-create the current version of the particular software program from the most-recent non-defective version of the particular software program, depending on which approach is faster.

Defect resolution in a software solution

One or more microservice flows affected by a microservice failure are determined. An amount of revenue loss per period of time for the one or more microservice flows affected by the microservice failure is determined. A microservice restoration time for the microservice failure is retrieved. An expected total cost of a downtime for each microservice is determined based on the amount of revenue loss per period of time and the microservice restoration time.

Methods, computer program products, and systems are presented. The method computer program products, and systems can include, for instance: receiving, by a database resource interface, a synthetic request to access a database resource; determining by machine logic rules of the database resource interface that the request has been synthetically generated by a generating device and is not a live production request; and responsive to the determination that the request has been synthetically generated sending, by the database resource interface, a responsive report to the generating device without accessing the database resource.

Disclosed herein is a method for predicting and avoiding request failures. The method includes receiving a request for access to at least one web service and analyzing the request to identify at least one probabilistic resource tree for handling the request. The method further includes detecting a problem preventing a usage of a resource in the at least one probabilistic resource tree. The problem causes the request to fail upon implementation of the request. Furthermore, the method includes performing an action to avoid the implementation of the request.

Avoiding web request failures before they occur by component analysis

A method and computer system for compiling, by a computing device, a list of hosting software classes included in the hosting software fix pack when a fix is available. An execution path of each application hosted on a hosting software may be recorded. The execution path may be stored in a data store for each application. It may be determined which operations of each application interact with the hosting software. The operations of each application used at runtime that interact with the hosting software may be stored, including storing invoked hosting software operations and classes used by the operations of each application. The invoked hosting software operations and classes may be compared with corresponding operations and classes provided in the list included in the hosting software fix pack. A list of each intersection of the comparison for each application impacted by the hosting software fix pack may be generated.

System and method for determining relevance of application software maintenance

The present invention is a system and method for forecasting and expanding software workload boundaries. The system includes a computer processor having a non-transitory memory containing program code for receiving a resource tree data set identifying a plurality of resources in a resource tree; receiving a sequence information set indicative of an order of resources for a request type; receiving a historical usage information set indicative of actual resource usage for the request type with respect resources in the resource tree; receiving a current throughput value for the request type; and determining, based at least in part upon the resource data tree set, the sequence information set and the current throughput values, a first additional potential throughput value corresponding to additional throughput with respect to the request type that can be performed by the resource tree in addition to its current throughput.

System and method for forecasting and expanding software workload boundaries

A computer-implemented method includes receiving a plurality of requests. Resource utilization is determined for two or more resources in an execution environment. An at-risk resource is identified, from among the two or more resources, with highest utilization among the two or more resources. The method further includes determining, by a computer processor, a subset of requests to be approved that are estimated to have lowest impact on the at-risk resource, based at least in part on historical resource utilization applicable to one or more request types of the plurality of requests. The subset of requests is approved for processing by the execution environment, where the subset of requests excludes one or more unapproved requests. The one or more unapproved requests are held in a waiting queue in lieu of processing the one or more unapproved requests, responsive to the one or more unapproved requests not being approved.

Scheduling requests in an execution environment

In service level agreement enforcement, a segmentation module intercepts a request for a current runtime environment, extracts request data from the request, and passes request data to a risk assessment component. The risk assessment component finds a request history profile matching the request data, determines a request impact on runtime environment resources from the request history profile, and obtains the current state of the current runtime environment. The risk assessment module determines the risk to the service level agreement associated with the request or any other request currently executing if the request is serviced in the current runtime environment, based on the request impact and the current state of the current runtime environment, and outputs the risk assessment to the segmentation module. When the risk assessment indicates a risk, the segmentation module passes the request to an isolated runtime environment. Otherwise, the request is passed to the current runtime environment.

Growing community of inventors

Durham, NC, United States of America

Samir Nasser