Patent classifications
G06F2201/87
AUTOMATED MODEL GENERATION FOR A SOFTWARE SYSTEM
Transaction data is accessed that has been generated from monitoring of a plurality of transactions in a system that includes a plurality of software components. The transaction data is assessed to identify that a particular one of the plurality of transactions meets a particular one of a set of conditions based on an attribute of the particular transaction. A portion of the transaction data describing the particular transaction is selected based on the particular transaction meeting the particular condition. A model of a particular one of the software components involved in the particular transaction is generated using the selected portion of the transaction data. The model is used to launch a computer-implemented simulation of the particular software component within subsequent transactions of the system.
SCENARIO COVERAGE IN TEST GENERATION
Transaction data is generated during monitoring of a plurality of transactions in a system and a respective flow is determined, from the transaction data, for each of the plurality of transactions. Each of the determined flows involves participation of a respective subset of software components of the system. A plurality of sets of overlapping flows in the plurality of flows are determined and a particular one of the plurality of sets of overlapping flows is determined to correspond to a use scenario of the system. A measure of the degree to which a set of artifacts modeling the system corresponds to the use scenarios of the system is determined.
CATALOGING METADATA FOR REPLICATION MANAGEMENT AND RECOVERY
A method and system for managing backup storage of file system entities. In an aspect, a file system catalog includes a database populator tool that generates records within a metadata table that may be maintained within a database. In response to detecting a replication cycle, the populator tool reads a stream of replication operations. For each of the replication operations, the populator tool determines the type of operation and in response to determining that a directory inode is an operand of the replication operation, the tool generates one or more catalog records. Each of the generated records includes and logically associates data entries corresponding to an inode number, a parent inode number, an entity type, a point-in-time-image (PTI) ID, an absolute path, and an operation.
SYSTEM AND METHOD FOR ANNOTATING CLIENT-SERVER TRANSACTIONS
According to one embodiment, a method for annotating client-server transactions with a computer executing software comprises receiving a stream of transactional data associated with a plurality of events on the computer, wherein the plurality of events correspond to one or more actions taken by a user of a computer, and partitioning the stream of transactional data into a plurality of portions. The method further comprises sorting the plurality of portions into one or more groups based on the similarity of one portion of the plurality of portions to another portion of the plurality of portions, and receiving non-transactional data, comprising information about the plurality of events, from the computer. The method may also comprise identifying, for each group of the one or more groups, based on the non-transactional data, a possible action of the one or more actions taken by the user and labeling each group based on the identification.
SELF-HEALING VIRTUALIZED FILE SERVER
In one embodiment, a system for managing a virtualization environment comprises a plurality of host machines, one or more virtual disks comprising a plurality of storage devices, a virtualized file server (VFS) comprising a plurality of file server virtual machines (FSVMs), wherein each of the FSVMs is running on one of the host machines and conducts I/O transactions with the one or more virtual disks, and a virtualized file server self-healing system configured to identify one or more corrupt units of stored data at one or more levels of a storage hierarchy associated with the storage devices, wherein the levels comprise one or more of file level, filesystem level, and storage level, and when data corruption is detected, cause each FSVM on which at least a portion of the unit of stored data is located to recover the unit of stored data.
SERVICE DEMAND BASED PERFORMANCE PREDICTION USING A SINGLE WORKLOAD
Systems and methods for service demand based performance prediction using a single workload is provided to eliminate need for load testing. The process involves identifying a range of concurrencies for the application under test; capturing a single workload pertaining to the application under test; and iteratively performing for the identified range of concurrencies: generating an array of one or more predefined CPU performance metrics based on the captured single workload; generating an array of service demands based on the captured single workload and the generated array of the one or more pre-defined CPU performance metrics; computing an array of throughput based on the generated array of service demands; and updating the generated array of the one or more pre-defined CPU performance metrics based on the computed array of throughput.
Multiple transaction logs in a distributed storage system
In various embodiments, methods and systems for implementing multiple transaction logs in a distributed storage system are provided. A log stream component detects performance metrics of a plurality of log streams. The performance metrics are associated with requests from partitions in the distributed storage system. A transaction component receives a request to execute a transaction using a log stream. The request is received from a partition of the distributed storage system. The performance metrics of the plurality of log streams can be referenced, where the performance metrics indicate a performance capacity of a selected log stream to process the request. A log stream for executing the transaction is determined based on the performance capacity. The log stream selected can also factor request attributes of the request. The transaction component communicates the request to be executed, using the log stream to perform the transaction.
APPLICATION CAPACITY FORECASTING
Systems and methods forecast processing capacity by monitoring historical key performance indicators (KPIs). The KPIs include measured values relating to a number of transactions that can be processed in parallel, an average number of transactions currently being processed, and an average amount of time to process each current transaction. One or more query parameters are received to query stored KPI data corresponding to the monitored historical KPIs. A forecasted processing volume level based on predicted values determined from a predictive model of the stored KPI data. The method also comprises generating an alert in response to the processing volume level being forecast to exceed a defined threshold is generated, thereby providing more reliable capacity monitoring and prediction of problems with processing applications that may otherwise go undetected until performance impacts occur.
IN-MEMORY JOURNALING
Systems and methods for indexing and searching an event log to determine whether an object of a file system is current. An example method may comprise: arranging a plurality of events into multiple segments, the plurality of events comprising operations affecting a plurality of objects; generating multiple indexes in view of the one or more segments, the indexes comprising a composite index representing the plurality of objects modified by the plurality of events; and inspecting the composite index to determine an object of the plurality of objects is modified by at least one of the plurality of events.
Optimization of Power and Computational Density of a Data Center
Techniques for optimizing power and computational density of data centers are described. According to various embodiments, a benchmark test is performed by a computer data center system. Thereafter, transaction information and power consumption information associated with the performance of the benchmark test are accessed. An efficiency metric value is then generated based on the transaction information and the power consumption information. In some implementations, the efficiency metric value indicates a number of transactions executed via the computer data center system during a specific time period per unit of power consumed in executing the transactions during the specific time period. The generated efficiency metric value is then compared to a target threshold value. Thereafter, a performance summary report indicating the generated efficiency metric value, and indicating a result of the comparison of the generated efficiency metric value to the target value, is generated.