If I set statistic-sampling-enabled=false, I don't see any rate stats
either.

Sushil: How are you setting enable-time-stats=true? Do you have a server
log you can post?

Thanks,
Barry Oglesby


On Thu, Jul 7, 2016 at 9:36 AM, Swapnil Bawaskar <[email protected]>
wrote:

> Hi Sushil,
> According to the docs
> <http://geode.docs.pivotal.io/docs/reference/topics/gemfire_properties.html>,
> you need to set two more properties as described below:
> enable-time-statistics Boolean instructing the system to track time-based
> statistics for the distributed system and caching. Disabled by default for
> performance reasons and not recommended for production environments. You
> must also configurestatistics-sampling-enabled to true and specify a
> statistics-archive-file. false
>
> On Thu, Jul 7, 2016 at 9:10 AM, Chaudhary, Sushil (CONT) <
> [email protected]> wrote:
>
>> Barry,
>> Thanks for the below.
>>
>> I have had enable-time-statistics=true in gemfire.properties. But still I
>> do see lantecies as 0. Am I missing something ?
>>
>> Cluster-wide Region Metrics
>>
>>
>> Category  |            Metric            | Value
>>
>> --------- | ---------------------------- | -------
>>
>> cluster   | member count                 | 2
>>
>>           | region entry count           | 7453666
>>
>> region    | lastModifiedTime             | -1
>>
>>           | lastAccessedTime             | -1
>>
>>           | missCount                    | -1
>>
>>           | hitCount                     | -1
>>
>>           | hitRatio                     | -1
>>
>>           | getsRate                     | 33158
>>
>>           | putsRate                     | 16580
>>
>>           | createsRate                  | 0
>>
>>           | destroyRate                  | 0
>>
>>           | putAllRate                   | 0
>>
>> partition | putLocalRate                 | 16580
>>
>>           | putRemoteRate                | 0
>>
>>           | putRemoteLatency             | 0
>>
>>           | putRemoteAvgLatency          | 0
>>
>>           | bucketCount                  | 113
>>
>>           | primaryBucketCount           | 113
>>
>>           | numBucketsWithoutRedundancy  | 0
>>
>>           | totalBucketSize              | 7453666
>>
>>           | averageBucketSize            | 32980
>>
>> diskstore | totalEntriesOnlyOnDisk       | 0
>>
>>           | diskReadsRate                | 0
>>
>>           | diskWritesRate               | 0
>>
>>           | totalDiskWriteInProgress     | 0
>>
>>           | diskTaskWaiting              | 0
>>
>> callback  | cacheWriterCallsAvgLatency   | 0
>>
>>           | cacheListenerCallsAvgLatency | 0
>>
>> eviction  | lruEvictionRate              | 0
>>
>>           | lruDestroyRate               | 0
>>
>>
>> *Sushil Chaudhary*
>> *Email*: [email protected]
>>
>> From: Barry Oglesby <[email protected]>
>> Reply-To: "[email protected]" <
>> [email protected]>
>> Date: Wednesday, July 6, 2016 at 5:43 PM
>>
>> To: "[email protected]" <[email protected]>
>> Subject: Re: Monitoring the latency and disc through put
>>
>> You can also use the gfsh show metrics command to see rates and latencies
>> like:
>>
>> gfsh -e "connect --locator=localhost[23456]" -e "show metrics
>> --region=/data"
>>
>> That will log output for the 'data' region like below.
>>
>> The rate stats are per second. The latency stats are in nanoseconds.
>> You'll need to set enable-time-statistics=true to see latencies.
>>
>> Executing - show metrics --region=/data
>>
>> Cluster-wide Region Metrics
>>
>> Category  |            Metric            | Value
>> --------- | ---------------------------- | ------
>> cluster   | member count                 | 2
>>           | region entry count           | 10000
>> region    | lastModifiedTime             | -1
>>           | lastAccessedTime             | -1
>>           | missCount                    | -1
>>           | hitCount                     | -1
>>           | hitRatio                     | -1
>>           | getsRate                     | 0
>>           | putsRate                     | 10396
>>           | createsRate                  | 0
>>           | destroyRate                  | 0
>>           | putAllRate                   | 0
>> partition | putLocalRate                 | 5189
>>           | putRemoteRate                | 5207
>>           | putRemoteLatency             | 160965
>>           | putRemoteAvgLatency          | 163281
>>           | bucketCount                  | 226
>>           | primaryBucketCount           | 113
>>           | numBucketsWithoutRedundancy  | 0
>>           | totalBucketSize              | 20000
>>           | averageBucketSize            | 44
>> diskstore | totalEntriesOnlyOnDisk       | 0
>>           | diskReadsRate                | 0
>>           | diskWritesRate               | 0
>>           | totalDiskWriteInProgress     | 0
>>           | diskTaskWaiting              | 0
>> callback  | cacheWriterCallsAvgLatency   | 0
>>           | cacheListenerCallsAvgLatency | 0
>> eviction  | lruEvictionRate              | 0
>>           | lruDestroyRate               | 0
>>
>>
>> Thanks,
>> Barry Oglesby
>>
>>
>> On Wed, Jul 6, 2016 at 2:31 PM, Chaudhary, Sushil (CONT) <
>> [email protected]> wrote:
>>
>>> Thanks John, let me try with the same.
>>>
>>> *Sushil Chaudhary*
>>>
>>>
>>> From: John Blum <[email protected]>
>>> Reply-To: "[email protected]" <
>>> [email protected]>
>>> Date: Wednesday, July 6, 2016 at 5:21 PM
>>> To: "[email protected]" <[email protected]>
>>> Subject: Re: Monitoring the latency and disc through put
>>>
>>> You have to *enable stats* on your application-defined *Regions*.
>>>
>>> You do that via the API
>>> <http://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/RegionFactory.html#setStatisticsEnabled(boolean)>
>>>  [1],
>>> or with cache.xml
>>> <http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/cache_xml.html#region-attributes>
>>> [2] (search for statistics-enabled) for via Spring Data GemFire, by
>>> example...
>>>
>>> <gfe:partitioned-region id="Example" statistics="true"/>
>>>
>>> Note, the default value is *false*, since recording statistics will
>>> incur more overhead.
>>>
>>> Hope this helps.
>>>
>>> Cheers,
>>> John
>>>
>>>
>>> [1]
>>> [2] http://gemfire.docs.pivotal.io/docs-gemfire
>>> /latest/reference/topics/cache_xml.html#region-attributes
>>>
>>>
>>> On Wed, Jul 6, 2016 at 2:12 PM, Chaudhary, Sushil (CONT) <
>>> [email protected]> wrote:
>>>
>>>> Hi,
>>>> I am using geode with Apex. Can anyone please guide me how can I
>>>> monitor latency and through put for each get and put.
>>>>
>>>> I am not getting stars on Geode UI, it always says Zero.
>>>>
>>>> *Sushil Chaudhary*
>>>> *Cell #:* 408-466-2004
>>>> *Email*: [email protected]
>>>>
>>>> ------------------------------
>>>>
>>>> The information contained in this e-mail is confidential and/or
>>>> proprietary to Capital One and/or its affiliates and may only be used
>>>> solely in performance of work or services for Capital One. The information
>>>> transmitted herewith is intended only for use by the individual or entity
>>>> to which it is addressed. If the reader of this message is not the intended
>>>> recipient, you are hereby notified that any review, retransmission,
>>>> dissemination, distribution, copying or other use of, or taking of any
>>>> action in reliance upon this information is strictly prohibited. If you
>>>> have received this communication in error, please contact the sender and
>>>> delete the material from your computer.
>>>>
>>>
>>>
>>>
>>> --
>>> -John
>>> 503-504-8657
>>> john.blum10101 (skype)
>>>
>>> ------------------------------
>>>
>>> The information contained in this e-mail is confidential and/or
>>> proprietary to Capital One and/or its affiliates and may only be used
>>> solely in performance of work or services for Capital One. The information
>>> transmitted herewith is intended only for use by the individual or entity
>>> to which it is addressed. If the reader of this message is not the intended
>>> recipient, you are hereby notified that any review, retransmission,
>>> dissemination, distribution, copying or other use of, or taking of any
>>> action in reliance upon this information is strictly prohibited. If you
>>> have received this communication in error, please contact the sender and
>>> delete the material from your computer.
>>>
>>
>>
>> ------------------------------
>>
>> The information contained in this e-mail is confidential and/or
>> proprietary to Capital One and/or its affiliates and may only be used
>> solely in performance of work or services for Capital One. The information
>> transmitted herewith is intended only for use by the individual or entity
>> to which it is addressed. If the reader of this message is not the intended
>> recipient, you are hereby notified that any review, retransmission,
>> dissemination, distribution, copying or other use of, or taking of any
>> action in reliance upon this information is strictly prohibited. If you
>> have received this communication in error, please contact the sender and
>> delete the material from your computer.
>>
>
>

Reply via email to