简体   繁体   English

在Asp.net 4.0上实现memchached

[英]implement memchached on Asp.net 4.0

I am new in memchached concept. 我是机电一体化概念的新手。 I search everywhere but i couldn't find anything how to implement in ASP.net 4.0. 我到处搜索,但是找不到任何如何在ASP.net 4.0中实现的东西。 Can anyone tell me about the right concept. 谁能告诉我正确的概念。

I successfully installed memchached Server in services.msc Now what to do after this step. 我已经在services.msc中成功安装了memchached Server,现在执行此步骤之后该怎么办。

can any one have good example in Asp.net. 谁能在Asp.net中有个很好的例子。 If yes, Please provide me. 如果是,请提供我。 OR Please tell me step by step code. 或请告诉我分步代码。

I also read these article http://rsuharta.wordpress.com/2011/04/27/memcached-provider-in-the-net-web-application/ 我也阅读了这些文章http://rsuharta.wordpress.com/2011/04/27/memcached-provider-in-the-net-web-application/

But didn't understand anything. 但是什么都不懂。 Please provide me best solution 请给我最好的解决方案

Thanks. 谢谢。

Here is a CodeProject article walking you through using memcached in an ASP.NET application. 这是一篇CodeProject文章,引导您逐步在ASP.NET应用程序中使用memcached。

However, let me first say that it's awful likely that if you don't already understand the concept of a framework like memcached you don't need it. 但是,首先让我说,如果您还不了解像memcached这样的框架的概念,那么就不需要它了,这很可怕。

Let me try and make this as clear as possible so you can make the right decision. 让我尝试使其尽可能清楚,以便您做出正确的决定。 For some reason, as of late, data caching has become the new "golden hammer" and all kinds of frameworks have popped up. 由于某种原因,最近,数据缓存已成为新的“金锤”,并且各种框架都已出现。 But the problem is that most developers don't understand the real driving forces behind implementing data caching and they don't understand that it's really not a trivial matter. 但是问题在于,大多数开发人员不了解实现数据缓存的真正推动力也不了解这并不是一件小事。 I'm going to give you the same example I gave someone else just yesterday on SO, but a paraphrased version. 我要给你的例子与我昨天昨天在SO上给别人的例子相同,只是释义。

Imagine if you will an application stack (ie more than one application) that accesses a shared set of data at a rate of more than, and I'm going to give you the real number , 40M+ transactions per day. 想象一下,如果您要使用一个应用程序堆栈(即一个以上的应用程序)以大于的速率访问一组共享数据,那么我将为您提供每天4,000万笔以上真实交易数。 Now, when I use the term transaction here I really mean read or write. 现在,当我在这里使用事务一词时,我的意思是读写。 Which only complicates things BTW because now I have to optimize for both. 顺便说一句,这只会使事情复杂化,因为现在我必须针对两者进行优化。

Alright, so now we have a set of applications accessing this shared data at a ridiculous rate per day - how do we ensure reasonable response times for both read and write? 好了,所以现在我们有一组每天以荒谬的速度访问该共享数据的应用程序-我们如何确保读写合理的响应时间? Data caching. 数据缓存。 But, if you're not sitting in that boat you probably don't need data caching and need to spend your time learning other things that are more relevant to what you're doing. 但是,如果您不坐在那条船上,则可能不需要数据缓存,而需要花时间学习与您的工作更相关的其他事情。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM