[ 
https://issues.apache.org/jira/browse/GEODE-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406588#comment-15406588
 ] 

ASF subversion and git services commented on GEODE-1724:
--------------------------------------------------------

Commit fa36a0c38c82e6157ecb9f7f4ca03a310951029b in incubator-geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=fa36a0c ]

GEODE-1724 Now thread updates Cq stats using ClientUpdateMessage.

Earlier it was feting value from disk.


> For updating client cq stats, we should not go to disk
> ------------------------------------------------------
>
>                 Key: GEODE-1724
>                 URL: https://issues.apache.org/jira/browse/GEODE-1724
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>            Reporter: Hitesh Khamesra
>            Assignee: Hitesh Khamesra
>
> durable client -queue with overflow, In this case overflow client queue uses 
> LIFO policy. Because of that we put new entry on disk first. But, after 
> putting that entry into queue that thread needs to update Cq stats, which 
> causes that thread to fetch that value again from disk. that hurts 
> performance. we should be updating any(all) client stats before putting that 
> value into disk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to