Abstract:
Occurrences of a particular event in an electronic device are counted by incrementing an event counter each time a variable number of the particular events have occurred, and automatically increasing that variable number as the total count increases. The variable number (prescale value) can increase geometrically according to a programmable counter base each time the count mantissa overflows. The event counter thereby provides hardware-implemented automatic prescaling while significantly reducing the number of interface bits required to support very large count ranges, and retaining high accuracy at very large event counts.
Abstract:
Methods and systems for providing software power analysis. In an example, a computerized method, and system for performing the method includes determining at least one performance monitoring counter value for at least one processor. A frequency of operation is determined for the processor. A power dissipation level is calculated for the processor using a computing device and the power dissipation level is provided as an output. In an example, at least one application programming interface is received. In an example, at least one application is run. In an example, a default file is generated. The default file contains at least one power model parameter and at least one estimated frequency of operation. In an example, several performance monitoring counter values are generated for at least one core in a multi-core processor. In an example, a software power analyzer control thread is executed.
Abstract:
Mechanisms for measuring, analyzing, and presenting performance data associated with a memory controller system are described. The mechanisms include a performance monitor that detects and analyzes performance including efficiency and latency of a memory controller system. In addition to determining performance, the systems identifies reasons for loss of memory controller system efficiency. Moreover, the reasons, the efficiency, and the latency are analyzed and presented in a manner easily understandable to a user.
Abstract:
A monitoring facility that is operable in two modes allowing compatibility with prior existing monitoring facilities. In one mode, in response to encountering a monitored event, an interrupt is generated. In another mode, in response to encountering a monitored event, one or more associated counters are incremented without causing an interrupt.
Abstract:
An apparatus, processor, and method for synchronizing trace data. A processor includes multiple cores, and each core operates at a different local clock frequency. A global clock is distributed to each core, and a timestamp is generated using the global clock and the local clock. The timestamp and a local clock saturation value are included in each trace entry, and the local clock saturation value is equal to the ratio between the local clock and the global clock. The trace entries from separate cores are time-correlated in a post-processing phase based on the timestamp and local clock saturation values.
Abstract:
A computer configuration utility automatically alters system configuration parameters to sample multiple different configurations. At least one workrate metric is measured at each sampled configuration. The workrate measurements for the multiple different configurations are compared to determine the effect of different configurations with respect to at least one optimization criterion. System configuration is automatically adjusted to the optimum configuration. Preferably, the workrate metric is (non-idle) instructions executed per unit of time.
Abstract:
Methods and structure for automated determination and reconfiguration of the size of a cache memory in a storage system. Features and aspects hereof generate historical information regarding frequency of hits on cache lines in the cache memory. The history maintained is then analyzed to determine a desired cache memory size. The historical information regarding cache memory usage may be communicated to a user who may then direct the storage system to reconfigure its cache memory to a desired cache memory size. In other embodiments, the storage system may automatically determine the desired cache memory size and reconfigure its cache memory. The method may be performed automatically periodically, and/or in response to a user's request, and/or in response to detecting thrashing caused by least recently used (LRU) cache replacement algorithms in the storage system.
Abstract:
A method includes receiving event information corresponding to an event associated with the operation of a system. The method also includes identifying related event information corresponding to a plurality of events that occurred before the event, wherein the event is related to the plurality of events. The method also includes storing the event information and the related event information as a group of events. The method further includes determining whether the group of events occurred within a first specified amount of time by identifying a time window ending at the occurrence of the event and beginning the first specified amount of time before the occurrence of the event and determining whether each event of the group of events occurred during the identified time window. The method further includes identifying an incident associated with the group of events upon determining that the group of events occurred within the first specified amount of time.
Abstract:
Collecting usage data in a cluster computing environment. A method includes at a tracker service receiving a request from an at least partially cloud based deployment for an interval for the deployment to report usage information in usage reports. The usage information includes information defining how software in a deployment is used. In response to the request from the deployment, the method further includes, the tracker service providing an interval to the deployment. The method further includes at the tracker service, receiving usage reports from the deployment according to the provided interval.
Abstract:
A system and method are described herein that provide performance data based on a monitoring of the performance on the end user side. A client application running on a user terminal is instrumented to record client performance counters on the user side. An application server matches the performance counters from the user side and performance counters obtained from the server side having the same transaction identification number. The system and method provides an end-to-end view of the user's perceived performance based on the transactions made by the user.