Abstract:
Technologies are described herein for collecting client-side performance metrics and latencies. A web page received by a web browser application executing on a user computing device includes markup or scripting code that instructs the browser to collect performance measures during the rendering of the content of the web page. The performance measures may include operation timings that measure the time it takes for a particular operation to complete during the rendering of the content and/or event counters that count the number of times that a specific event occurs during the rendering of the content. The web browser application sends an event report containing the collected performance measures to a reporting module executing on a server computer. The reporting module receives the event report, validates the content of the event report, and adds the event report to a database or other data storage system.
Abstract:
Embodiments of automated cloud service performance prediction are disclosed. The automated cloud service performance prediction includes extracting one or more dependency relationships for each web object in the webpage. The prediction further includes determining an original performance metric value and original timing information associated with a page loading of a webpage. The prediction also includes simulating a page loading of the webpage based on the adjusted timing information and the dependency relationships to estimate a new performance metric value associated with the simulated page loading of the webpage. The prediction additionally includes comparing the original performance metric value to the new performance metric value to determine whether the adjusted timing information increased or decreased the new performance metric value relative to the original performance metric value.
Abstract:
A computer-implemented method includes scanning a clip of messages that includes message requests and message responses arranged in a sequence. The scanning is performed based on one or more search parameters and produces a list of one or more name/value pairs. The clip is utilized to perform a load test on a target website. Each name/value pair has a corresponding value. For each name/value pair in the list a message request in the clip is identified where the corresponding value is first used. Then, looking backwards in the sequence from the message request where the corresponding value is first used, prior message responses are located where the corresponding value is found. An extraction point is specified in the clip for the corresponding value as a latest message response in the sequence where the corresponding value was returned from the target website. The corresponding value is then stored as a property.
Abstract:
An amount of a resource, such as bandwidth, needed to successfully accomplish a target Recovery Point Objective (RPO) is estimated in a data processing environment giving two or more physical or virtual data processing machines. Time-stamped samples of a usage metric for the resource are taken over a usage period. These samples are later accessed and time aligned to determine an average usage metric at defined intervals. An expected tolerance for RPO failure allows determining a first assumed amount of the resource available to achieve a target RPO that is less than might otherwise be expected. These steps can be repeated for other expected replication failure tolerances to allow a risk versus resource available trade off analysis.
Abstract:
This patent application pertains to capturing web-based scenarios. One example detects execution of a web application. This example also automatically captures non-deterministic events of the execution in a manner that is transparent to a user of the web application.
Abstract:
Techniques for gauging performance of services are provided. A client agent is configured to process on a client and simulates operations of a transaction as instructed by a server agent. The client agent also gathers metrics for each of the operations as they process on the client and passes the metrics back to the server agent. The server agent analyzes the metrics in accordance with a policy and takes one or more actions in response thereto.
Abstract:
Transaction-segregated metrics are obtained for component invocations of different transactions of an application. Corresponding tree data structures are maintained by an agent and a manager which describe sequences of invoked components of the different transactions. The start and end of each component are each represented by a node in each branch of the tree data structure. Each transaction is identified by matching a branch to a transaction trace. Gatherers are linked to one or more nodes to collect the transaction-segregated metrics. For example, metrics can be gathered separately for component invocations in different transactions. Metrics can also be gathered together for instances of different components in one or more transactions. A user interface includes a directed graph having vertices connected by edges. Edge portions are visually distinguished from one another based on the metrics of the gatherers. Each edge portion can be associated with one or more of the gatherers.
Abstract:
Embodiments of the invention provide the ability to determine whether a particular application may be safely added to a client computing device. Further, embodiments of the invention also allow for performing a rollback operation on clients experiencing a decrease of performance due to an addition of new software. For example, after a client updates to a new piece of software, a server may monitor the performance of the first client by analyzing a plurality of updates received from the first client. Each update may include a performance indicator. Using the updates, the server may detect a decrease in the performance of the first client. Upon detecting the decrease in the performance, the server may initiate a rollback to a previous state on the first client.
Abstract:
Network data associated with a network session is captured at a first location. The network data includes, but is not limited to, web page data transmitted over a network between a web server and a user terminal. User interface events associated with the same network session are separately captured at a second user terminal location. The user interface events include, but are not limited to, user inputs for interacting with the web page data. Both the captured network data and the separately captured user interface events are then used for analyzing the network session.
Abstract:
Operability of a web application comprising dynamic contents is evaluated continuously with high precision. In a web application execution system 1000, a web server apparatus 121 responsive to a request from a client apparatus 101 and a log server apparatus 141 are connected via a network 161. The log server apparatus 141 stores an operation log obtained when the web application is operated on the web browser in accordance with a manual having a description of an operation method of the web application, as a first operation log, stores another operation log obtained when the web application is operated in the client apparatus 101, as a second operation log, and transmits difference information between the first and second operation logs to the web server apparatus 121, the client apparatus 101 or a different external apparatus 181 to cause the difference information to be at least displayed or recorded.