Abstract: A method includes receiving, by a client, from an identity service provider, an authentication token associated with a user of the client. The method also includes receiving, by the client, from a control plane, an authorization token associated with a cloud resource. The method also includes receiving, by a desktop agent, a password request including the authentication token and the authorization token. The method also includes validating the password request based at least in part on the authentication token and the authorization token. The method also includes responsive to the validating the password request, receiving, by the client, a password for the cloud resource. The method also includes causing the client to transmit the password to the cloud resource to establish a connection between the client and the cloud resource.

Abstract: A method is provided for testing a trading system having a verification subsystem and trading environments. Each of the environments has a network interface, memory, and a matching engine executed by a processor. The method includes retrieving, by the verification subsystem, at least one defined use case. Each defined use case includes command lines. The method also includes parsing the command lines based on defined parsing rules to produce parsed command lines. Each parsed command line includes a verb specifying financial transactions. Each parsed command line also includes data fields. The method further includes mapping the verb and fields of each command line based on defined mapping relationships to generate a test case. The method also includes executing the test case to generate messages to be executed by the trading system. The method also includes reading parameters of the trading system for comparison to specified validation values.

Abstract: A method is provided for testing a trading system having a verification subsystem and trading environments. Each of the environments has a network interface, memory, and a matching engine executed by a processor. The method includes retrieving, by the verification subsystem, at least one defined use case. Each defined use case includes command lines. The method also includes parsing the command lines based on defined parsing rules to produce parsed command lines. Each parsed command line includes a verb specifying financial transactions. Each parsed command line also includes data fields. The method further includes mapping the verb and fields of each command line based on defined mapping relationships to generate a test case. The method also includes executing the test case to generate messages to be executed by the trading system. The method also includes reading parameters of the trading system for comparison to specified validation values.

Abstract: Embodiments of the present invention are described which pertain to methods and systems of generating and evaluating potential resource allocations for an application. In one embodiment, metrics are associated with an application. Measurements for the metrics of the application are calculated. Potential resource allocations are generated based on the measurements of the metrics. A subset of the potential resource allocations are evaluated using a statistical model of the operation of the application.

Abstract: Embodiments of the present invention that pertain to methods and systems for the calculation of resource requirements for a composite application are described. In one embodiment, information describing what component applications are associated with the composite application is received. Information describing metrics that are to be measured for the component applications is received. Information describing interrelationships between the component applications associated with the composite application is received. Information describing rules for calculating the resource requirements for the component applications is received. The rules are based on the interrelationships between the component applications and the metrics that are to be measured.

Abstract: One embodiment relates to a method for identifying sources of memory retention in an executing application. A size of a set of objects is tracked over multiple periods. A period is determined to be a growth period if the size for the set of objects increases above a previous maximum size, and the number of growth periods is counted. The set of objects is flagged as having potential undesired object retention (a memory leak) if the number of growth periods is greater than a threshold number. Other embodiments are also disclosed.

Abstract: Embodiments of the invention relate to identifying sources of memory leaks. In an embodiment, an agent collects information related to object allocations and de-allocations in accordance with a sampling period, and, based on the relationship between object allocations and de-allocations, the agent analyzes the data and reports the results. Other embodiments are also disclosed.

Abstract: One embodiment disclosed relates to a method of automated alerts for resource retention problems. Data on the resource usage as a function of time is obtained, and an automated analysis of the resource usage data is performed to determine whether the data indicates a minimum level of retention of the resource that increases over time for a period of time longer than a threshold time period. An alert notification is provided if the analysis determines that said indication is inferred from the data. Other embodiments are also disclosed.

Abstract: Embodiments of the invention distribute profiling responsibilities for a clustered application to various instances of the application that generally run on different computer hosts. In an embodiment, the profiling responsibility is measured in terms of metrics wherein each profiling agent of an instance collects metrics about that instance. The metrics are prioritized and assigned to instances such that the highest priority metrics are assigned if possible. Each metric is associated with an expected performance overhead, and the assignment of metrics to an instance is done such that the performance overhead on that instance and/or host does not exceed a threshold. Other embodiments are also disclosed.

Abstract: One embodiment disclosed relates to a method of finding lock contention in an application with concurrent threads. Status data is retrieved by periodically sampling status of said threads. The periodically-sampled status data is accumulated, and the lock contention is statistically found from the accumulated status data. The status data may include location information that is usable to pinpoint the lock contention.