How is PCP different from tools like vmstat, ps, top, etc?
Each of these standard Linux tools: • collects a predefined mix of metrics • understands the syntax and semantics of the various “stat” files below /proc • involves no IPC or context switches associated with synchronous IPC • only monitors the local host and cannot monitor a remote host • cannot replay historical data Each of these standard Linux tools could also be re-implemented over the PCP protocols, in which case they would each: • collect a predefined mix of metrics • be insulated from how the data is extracted, and have access to the explicit data semantics over the PCP APIs • optionally (and typically) involve IPC and context switches associated with synchronous IPC • monitor the local host or a remote host with equal ease and no application program changes • process real-time or historical data with equal ease and no application program changes As a proof of concept, pmstat in the PCP Open Source release is a re-implementation of vmstat using the PCP APIs. In addition, new PCP
Related Questions
- Why does Page Speed return different results from those reported by Site Performance in Webmaster Tools?
- Why does Page Speed return different results from those reported by Site Performance in Webmaster Tools?
- How is Free Web Site Builder different from other online website creation tools that are available?
- Is it acceptable to have entry and exit data from different curriculum based assessment tools?
- Is it acceptable to have entry and exit data from different curriculum based assessment tools?
- How is PCP different from tools like vmstat, ps, top, etc?
