Server Counters

ScaleOut StateServer includes a complete set of Perfmon counters for monitoring each host’s health, memory usage, and access rates using Microsoft’s Perfmon performance measurement tool. These counters independently report statistics for each SOSS host. They do not report aggregate statistics for a complete SOSS distributed cache. The counters are listed under the ScaleOut StateServer Service performance object within Perfmon.

The following Perfmon counters are available for tracking the status of the specified SOSS host. Where applicable, these counters closely correspond to the corresponding status indications displayed by the SOSS management tools (see the Management section for details on SOSS management tools).

  • Host Joined: reports 1 if the local host is joined to the store or 0 if the host is inactive,

  • Host Ready: reports 1 if the local joined host is ready (i.e., able to accept client access requests) or 0 if the host is in a not-ready state,

  • Number of Joined Hosts: reports the number of joined hosts in the SOSS distributed store,

  • Percent Load: reports the percentage of the distributed store’s memory load that is being handled by the local StateServer service.

The following Perfmon counters are available for measuring memory usage and host access activity from clients or other SOSS hosts accessing objects stored on the specified SOSS host. These access rates closely correspond to the access rates displayed by the SOSS management tools and are always reported on a “per second” basis.

  • Objects: the total number of objects in this SOSS host (not including replicas),

  • Object Memory (bytes): the total object memory stored in this SOSS host, in bytes

  • Host Creates: the number of create operations performed on locally stored objects by the StateServer service per second,

  • Host Reads: the number of read operations performed on locally stored objects by the StateServer service per second,

  • Host Updates: the number of update operations performed on locally stored objects by the StateServer service per second,

  • Host Deletes: the number of delete operations performed on locally stored objects by the StateServer service per second.

The following Perfmon counters are available for measuring client access activity from local or remote clients making access requests directly to the specified SOSS host. These access rates do not correspond to the access rates displayed by the SOSS management tools and are tracked according to the sampling interval specified in Perfmon.

  • Client Connections: the total number of client connections to the StateServer service,

  • Remote Clients: the total number of remote client systems connected to the StateServer service,

  • Client Creates: the number of client create accesses performed during the sampling interval,

  • Client Reads: the number of client read accesses performed during the sampling interval,

  • Client Updates: the number of client update accesses performed during the sampling interval,

  • Client Deletes: the number of client delete accesses performed during the sampling interval,

  • Avg. Bytes Read: the number of bytes read per client read operation during the current sample interval,

  • Avg. Bytes Written: the number of bytes written per client create or update operation during the current sample interval,

  • Client Cache Read Hits: the number of read hits to all requesting client caches (i.e., the number of client read accesses for which the requesting client had the current version of the requested object in its client cache) during the sampling interval ,

  • Distributed Cache Read Misses: the number of read misses in the SOSS store (i.e., the number of client read accesses for which the requested object was not found) during the sampling interval,

  • Events Fired: the number of asynchronous client events fired by this SOSS host during the sampling interval.

  • Lock Collisions: the number of lock collisions that occurred during the sampling interval.

  • Locks Acquired: the number of locks acquired during the sampling interval.

The following Perfmon counters are available for measuring ScaleOut GeoServer access activity to/from remote SOSS stores by the specified SOSS host. These statistics are only used when the ScaleOut GeoServer option has been licensed and are tracked according to the sampling interval specified in Perfmon.

  • GeoServer Updates Sent: the number of GeoServer replication updates sent by this host during the sampling interval,

  • GeoServer Deletes Sent: the number of GeoServer replication deletes sent by this host during the sampling interval,

  • GeoServer Bytes Sent: the number of bytes sent per GeoServer update operation by this host during the sampling interval,

  • GeoServer Updates Received: the number of GeoServer replication updates received by this host during the sampling interval,

  • GeoServer Bytes Received: the number of bytes received per GeoServer update operation by this host during the sampling interval,

  • GeoServer Total Queue Length: the sum of the length of all GeoServer outbound replication queues for the local StateServer service.

The following Perfmon counters report statistics about the frequency of events that are delivered by a ScaleOut host to client applications. The types of events measured here include object expiration events, write-behind/refresh-ahead events, and server-side events triggered by ScaleOut ComputeServer/StreamServer operations.

  • Events Fired: the number of events fired by the local StateServer host during the sampling interval.

  • Events Not Fired: the number of events that were not fired by this StateServer host during the sampling interval. Events typically do not get fired because there is no client application registered to handle events.

  • Events Not Handled: the number of events fired by the local StateServer host that were not handled by the registered event-handling application. An event is marked as not handled because the client application either explicitly sets the event’s disposition to unhandled or because the application does not handle events for all application namespaces.

  • Single Method Invocations: the number of single method invocations (SMIs) performed on the local host during the sampling interval.

  • Posted Events: the number of ScaleOut StreamServer events that were posted to the local host during the sampling interval.