blocks|key|4431113|text|我没有一起使用它们，但我已经在单独的项目中使用了它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431114|最后，我看到文档明确地说，与web服务器共享是可以的。|4431115|Memcache实际上只需要内存，如果你不考虑asp.net缓存，那么你的web服务器实际使用了多少内存？可能不是很多。它不会在CPU上与你的web服务器竞争太多，而且它根本不需要磁盘。您可以考虑从传入的web请求中分割网络流量(如果您还没有这样做的话)。|4431116|它工作得很好，而且速度很快，我对它没有任何问题。|4431117|哦，失效在我使用它的项目上是明确的。不确定有什么其他模式可以这样做。|4431118|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Haven't used them together, but I've used them both on separate projects.

Last I saw the documentation explicitly said that sharing with the web server was ok.

Memcache really only needs RAM and if you take your asp.net cache out of the equation how much RAM is you web server actually using? Probably not much. It won't compete much with your web server for CPU and it doesn't need disk at all. You might consider segmenting off the network traffic (if you don't already) from the incoming web requests.

It worked well and was fast I didn't have any problems with it.

Oh, invalidation was explicit on the project I used it on. Not sure what other modes there are for that.

blocks|key|366744|text|最佳实践(根据memcached站点)是在与web服务器应用程序相同的机器上运行memcached，否则您将进行http调用(这并不是那么糟糕，但也不是最优的)。如果您运行的是64位应用程序服务器(如果要运行memcached，您可能应该这样做)，那么您可以为每个服务器加载大量内存，这些内存将可用于memcached。memcached使用的CPU资源不多，所以如果您当前的应用服务器负载不是很高，它将保持这种方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366745|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Best practice (according to the memcached site) is to run memcached on the same box as your web server app or else you're making http calls (which isn't all that bad, but it's not optimal). If you're running a 64-bit app server (which you probably should if you're going to be running memcached), then you can load up each of the servers with loads of memory and it will be available to memcached. There's not much in the way of CPU resources used by memcached, so if your current app server isn't very taxed, it will remain that way.

blocks|key|1046356|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1046357|+"memcached将负责将其分发到每个机器上“|blockquote|1046358|1046359|1046360|memcached不会将缓存分发或复制到memcached场中的每个机器。memcached客户端基本上对键进行散列，并根据散列选择缓存服务器。当一个memcached服务器发生故障时，您将丢失该服务器上存在的所有缓存项，但是，客户端将识别该故障并开始向另一个服务器写入值。在这种情况下，您的代码需要考虑缓存中缺少的项，并在必要时重置它们。|1046361|本文将更详细地讨论memcached架构：How+memcached+works。|offset|length|1046362|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/memcached/wiki/FAQ#How_does_memcached_work?^0|0|0|0|0|0|L|J|0|0^^$0|@$1|2|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|U|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|X|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|Y|7|@]|8|@$J|Z|K|10|1|11]]|9|$]]|$1|L|3|-4|4|5|6|12|7|@]|8|@]|9|$]]]|M|$N|$4|O|P|Q|9|$R|S]]]]

<blockquote>
 "memcached would handle distributing it on each box"
</blockquote>

memcached does not distribute or replicate a cache to each box in a memcached farm. The memcached client basically hashes the key and chooses a cache server based on that hash. When one of the memcached servers fail you will lose whatever cached items existed on that server, however, the client will recognize the failure and begin writing values to a different server. This being the case, your code needs to account for missing items in the cache and reset them if necessary.

This article discusses the memcached architecture in more detail: <a href="http://code.google.com/p/memcached/wiki/FAQ#How_does_memcached_work?" rel="noreferrer">How memcached works</a>.

blocks|key|366842|text|值得一看的是Velocity，这是微软提供的分布式缓存。我不能将它与memcached进行逐点比较，但是Velocity与ASP.NET集成在一起，并将继续得到更多的开发和集成。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|366843|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/data/cc655792.aspx^0|6|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Worth checking out <a href="http://msdn.microsoft.com/en-us/data/cc655792.aspx" rel="nofollow noreferrer">Velocity</a>, which is a distributed cache provided by Microsoft. I cannot give you a point-by-point comparison to memcached, but Velocity is integrated with ASP.NET and will continue to get more development and integration.

blocks|key|1051221|text|如果您想让复制访问您的memcached服务器，那么它可能值得一看repcached。这是一个用于memcached的补丁，用于处理复制部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1051222|entityMap|0|LINK|mutability|MUTABLE|url|http://repcached.lab.klab.org/^0|X|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you want to get replication accross your memcached servers then it maybe worth a look at <a href="http://repcached.lab.klab.org/" rel="nofollow noreferrer">repcached</a>. It's a patch for memcached that handles the replication part.

We have 22 HTTP servers each running their own individual ASP.NET Caches. They read from a read only DB that is only updated off peak hours.

We use a file dependency to invalidate the cache, prompting the servers to "new up" their caches...If this is accidentally done during peak hours, it risks bringing down our DB cluster due to the sudden deluge of open connections.

Has anyone used memcached with ASP.NET in this distributed form? It seems to me that it would offer a huge advantage of having to only build up one cache (and hit the DB 21 times less), while memcached would handle distributing it on each box.

If you have, do you place it on the same box as the HTTP boxes, or do you run a separate cache tier? How well does it scale, can we expect it to need powerful servers? Our working dataset is not huge (We fit it into 4 gigs of memory on each HTTP box just fine).

How do you handle invalidation?

Looking for experiences and war stories.

EDIT: Win2k3, IIS6, 64-bit servers...4 gigs per box (I believe, we may have upped it to 16 gigs when we changed to 64-bit servers).

Anyone using Memcached with ASP.NET on a distributed farm?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有22个HTTP服务器，每个服务器都运行自己的ASP.NET缓存。它们从只读数据库中读取数据，该数据库只在非高峰时间更新。我们使用文件依赖来使缓存无效，促使服务器“更新”它们的caches...If这是在高峰时间意外完成的，它可能会由于打开连接的突然泛滥而导致数据库集群宕机。有没有人在这种分布式形式中使用过memc...

问有人在分布式服务器场中使用Memcached和ASP.NET吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有人在分布式服务器场中使用Memcached和ASP.NET吗？EN