AppFabric错误的缓存大小 [英] AppFabric wrong cache size

查看:138
本文介绍了AppFabric错误的缓存大小的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有以下情况:

PowerShell命令    Get-CacheStatistics -CacheName CacheName ,返回以下内容:

PowerShell commands  Get-CacheStatistics -CacheName CacheName, return following:

尺寸        :5607491966

ItemCount   :-27343493

RegionCount :1024

RequestCount:313342002

MissCount   :79787005

Size         : 5607491966
ItemCount    : -27343493
RegionCount  : 1024
RequestCount : 313342002
MissCount    : 79787005

ie。它表示缓存大小为5.6Gb,在群集配置中最大缓存大小设置为6.1Gb,因此我经常逐出运行。

ie. It says that cache size is 5.6Gb, in cluster configuration max cache size set to 6.1Gb, and so i have very often eviction runs.

实际上  ; DistributedCache.exe进程占用大约1.6Gb内存。

But in reality DistributedCache.exe process takes about 1.6Gb of memory.

如何解释这个?

PS。 ItemCount低于零,因为我使用了悲观的concurency模型(我听说过这个bug)。

PS. ItemCount is below zero, because i use pessimistic concurency model (i hear about this bug).

推荐答案

我认为你的意思是DistributedCacheService。 exe进程?我澄清的唯一原因是我认为Beta版本和RTM版本之间的名称已经改变。

I assume you mean the DistributedCacheService.exe process? The only reason I'm clarifying is that I think the name was changed between Beta releases and the RTM version.

我需要问你在哪里查看服务的内存?如果是任务经理,您可能会看到"工作集"。由于太过分页到磁盘,它可能小于实际提交的内存量。您可能希望
使用性能监视器并查看进程的专用字节数(已提交的内存)以确定。如果你已经这样做了,我为这个假设道歉,我们会看看其他事情。

I need to ask where you are looking at the memory of the service? If it is task manager, there is a chance that you're looking at the "Working Set" which can be smaller than the actual amount of committed memory due too paging to disk. You might want to use Performance Monitor and look at Private Bytes of the process (committed memory) just to be sure. If you're already doing this, I apologize for the assumption and we'll look at other things.

Jason Roth

Jason Roth


这篇关于AppFabric错误的缓存大小的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆