Hi Song, I agree that this could be used for various things like
1. Overall overlay status information for the overlay deployer 2. Peer selection for neighbor table entries by topology plugins 3. And maybe also designating functionalities to nodes based on metrics observed Yes, there are other metrics from comon related to memory usage, bandwidth use which may also be useful. Thanks Saumitra From: Song Haibin [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2008 7:07 PM To: Das, Saumitra; [EMAIL PROTECTED] Cc: ietf@ietf.org Subject: RE: [P2PSIP] How to describe the processing power Dear Das, See inline. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Das, Saumitra Sent: Wednesday, November 12, 2008 5:12 PM To: [EMAIL PROTECTED] Cc: ietf@ietf.org Subject: Re: [P2PSIP] How to describe the processing power Dear Song, Processing power would be more informational in terms of CPU load. A good example of what would be useful would be to look at the comon monitoring tool (http://summer.cs.princeton.edu/status/) for the planetlab testbed. It uses the following metrics for selecting nodes based on CPU and I have found such selection to be very useful in determining the performance of a slice on the machine. [Song] It is also useful in selecting peer for a neighbor table entry, when there are multiple choices existing and for the overlay management to collect the overall status of the overlay. >From the comon site, these are some metrics that may be useful "CPU Speed Busy CPU Sys CPU Free CPU These fields give some insight into the CPU behavior of the node. The CPU Speed is just the speed of the processor in gigahertz. The Busy CPU field gives the % of time the CPU is utilized, and the Sys CPU field specifies what percentage of time the CPU is spending in the OS. Both of these values are the maximum values over the past 5 minutes. The Free CPU indicates how much of the CPU a spin-loop was able to obtain, giving some insight into how much of the node's CPU a new slice would receive." We could define these fields and leave it optional as to whether all of them are required. i.e. running a spin-loop may be expensive for some devices. [Song] This is helpful. I'm very glad to see this monitoring tool in the planetlab testbed. If it works well in the planet lab, we may have it included in the diagnostics draft after discussion. I also see other useful metrics for other parameters in the page (http://summer.cs.princeton.edu/status/). Best, Saumitra www.saumitra.info Date: Tue, 11 Nov 2008 15:12:21 +0800 From: Song Haibin <[EMAIL PROTECTED]> Subject: [P2PSIP] How to describe the processing power To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii Dear all, In p2psip diagnostics draft http://tools.ietf.org/id/draft-zheng-p2psip-diagnose-03.txt , we have some doubt about how to describe one of the diagnostic information: processing power. We propose to use the unit of MIPS to describe it. However, the Max number of connections may be another choice. Do you have any good suggestions? Best Regards, Song Haibin Email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Skype: alexsonghw
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf