Proposed Performance Counters for CTP4

We are planning to add performance counters in the upcoming release, CTP4. The performance counters will be available for one or both of the following categories:

·         Host - A category for single-instance performance counters pertaining to a single cache host. Host counters track information such as total active connections and total client requests for a single cache host.

·         Cache - A category for multiple-instance performance counters pertaining to all cache hosts. Each instance of a cache counter corresponds to a separate named cache in the cache cluster.

 

Counter Name	Description	Applicable Category
Total data size (MB)	This counter will represent total size of cached data in Velocity. It does not include cache overhead.	Host, Cache
Total cache misses	This will be total number of requests that couldn’t find the key in cache since the start of the cache service. This gives the information about how efficiently cache is being used.	Host, Cache
Cache miss ratio	This counter gives ratio of ‘number of requests that couldn’t find the key’ to the ‘total number of requests’ since the start of the cache service. And it gives the information about how efficiently cache is being used. It is a ratio of sum of misses to total number of request since the start of the cache service.	Host, Cache
Total Get requests	This will be number of Get requests received from all clients since the start of the cache service.	Host, Cache
Get miss ratio	This will be ratio of ‘number of Get requests which couldn’t find the key’ to the ‘total number of Get requests’. This gives the information about how efficiently cache is being used.	Host, Cache
Total write operations	This will be number of write requests since the start of the cache service. The write requests include Put, Add, Remove, ResetObjectTimeout, GetAndLock, PutAndLock, Unlock.	Host, Cache
Total active connections	This counter stores number of active connections on the cache host.	Host
Total client requests	This will be total number of requests received from the Velocity client. It includes all of the API calls.	Host
Total requests served	It is a counter for number of requests served and responses sent by the cache host since the start of the cache service. This will provide a rough estimate of the throughput of the cache host.	Host
Average response time (milliseconds)	This counter represents the average response time to service a Velocity client API request on the cache host. The average is taken over all the requests received by the cache host since the start of the cache service.	Host
Total expired Object	This counter stores the number of expired object since the start of the cache service.	Host
Total memory evicted (MB)	This will provide the information about the amount of memory which was freed due to the Eviction procedure on the cache host since the start of the cache service.	Host, Cache
Average age of evicted object (seconds)	It stores average age of evicted Object. This is measure of the efficiency of the eviction procedure.	Host, Cache
Total eviction run	This will be the number of eviction runs since the start of the cache service.	Host
Total evicted Objects	This counter stores the number of evicted object since the start of the cache service.	Host
Total exceptions	This represents the number of Velocity exceptions thrown by the cache host since the start of the cache service.	Host
Total retry exception	This will be total number of retry operation exceptions thrown by the cache host since the start of the cache service.	Host
Total notification poll requests	This counter stores total number of poll requests received by the cache host since the start of the cache service.	Host, Cache
Total GetAndLock requests	This will be total number of GetAndLock requests received by the cache host since the start of the cache service.	Host, Cache
Total successful GetAndLock requests	This will be number of successful GetAndLock requests since the start of the cache service.	Host, Cache

Look forward to your feedback on identified counters or suggestions for new counters.

Sharique Muhammed

(Microsoft project code named "Velocity" Team)

Comments

• Anonymous
  June 10, 2009
  Hey that looks really good! One more way for us to monitor Velocity. I think a lot of effort needs to go into the HA features. Like, we had to write custom scripts to make Velocity start up on a cold boot. That should not be necessary. Also, it appears as if we need 3 nodes to make sure we always have quorum. It'd be nice if it could use the SQL database as a 3rd party for quorum. Any word on encryption/authentication?

• Anonymous
  June 12, 2009
  It seems CTP3 is not compatible with windows 7. Install failed. Will CTP4 fix it? or is there anyway i can fix it manually before ctp4?

• Anonymous
  June 15, 2009
  Devido ao feedback de alguns testadores dos CTPs lançados até agora, o "Velocity" terá um CTP4 antes