请查看 Windows Server AppFabric。它包括 Microsoft .NET 应用程序分布式缓存（代号“Velocity”），用于提高 Web、复合和企业 .NET 应用程序的性能。
Check out Windows Server AppFabric. It includes Microsoft distributed cache for .NET apps (code name “Velocity”) that is used to improve performance of web, composite, and Enterprise .NET applications.
Improving performance is generally achieved by improving multiple areas of computing; RAM, CPU, disk speed / space, data cashing, network latency, horizontal and vertical partitioning, application factoid, compression, etc. If you are interested in improving your performance I would suggest looking at: http://highscalability.com/
You don't need NCache to have high performance or scalability. It looks like a cache-oriented in-memory database, and that's nifty for some applications, but not a general prerequisite for high performance or scalability.
Another option for achieving better performance and scaling in the caching front is via use of both RAM & Disk, specifically, the disk can be used to virtualize the memory, in somewhat like a memory extender fashion to solve scale as memory is scarce. That is, highly optimized, totally reduced mapping overheads. Low footprint, tightly integrated with the data indexing engine w/ direct mapping to disk.
Depending on use-case, there is no point using a caching solution when caching itself hasn't achieved optimal performance & scalability levels due to network & orchestration latencies.
发布评论
评论（4）
请查看 Windows Server AppFabric。它包括 Microsoft .NET 应用程序分布式缓存（代号“Velocity”），用于提高 Web、复合和企业 .NET 应用程序的性能。
Check out Windows Server AppFabric. It includes Microsoft distributed cache for .NET apps (code name “Velocity”) that is used to improve performance of web, composite, and Enterprise .NET applications.
提高性能通常是通过改进多个计算领域来实现的； RAM、CPU、磁盘速度/空间、数据缓存、网络延迟、水平和垂直分区、应用程序事实、压缩等。如果您有兴趣提高性能，我建议您查看：http://highscalability.com/
Improving performance is generally achieved by improving multiple areas of computing; RAM, CPU, disk speed / space, data cashing, network latency, horizontal and vertical partitioning, application factoid, compression, etc. If you are interested in improving your performance I would suggest looking at: http://highscalability.com/
您不需要 NCache 来获得高性能或可扩展性。它看起来像一个面向缓存的内存数据库，这对于某些应用程序来说非常有用，但并不是高性能或可扩展性的一般先决条件。
You don't need NCache to have high performance or scalability. It looks like a cache-oriented in-memory database, and that's nifty for some applications, but not a general prerequisite for high performance or scalability.
在缓存前端实现更好的性能和扩展的另一种选择是同时使用 RAM 和内存。磁盘，具体来说，磁盘可以用来虚拟化内存，有点像内存扩展器的方式，以解决内存稀缺时的扩展问题。也就是说，高度优化，完全减少了映射开销。占用空间小，与数据索引引擎紧密集成，直接映射到磁盘。
根据使用情况，当缓存本身未达到最佳性能时，使用缓存解决方案是没有意义的。由于网络和网络的可扩展性水平编排延迟。
该技术的一个非常好的示例实现是新的 Virtual Cache 开源代码库，请通过此链接查看更多详细信息：http://www.codeproject.com/Tips/827339/Virtual-Cache。
Another option for achieving better performance and scaling in the caching front is via use of both RAM & Disk, specifically, the disk can be used to virtualize the memory, in somewhat like a memory extender fashion to solve scale as memory is scarce. That is, highly optimized, totally reduced mapping overheads. Low footprint, tightly integrated with the data indexing engine w/ direct mapping to disk.
Depending on use-case, there is no point using a caching solution when caching itself hasn't achieved optimal performance & scalability levels due to network & orchestration latencies.
A very good sample implementation of this technique is the new Virtual Cache open source code library, check it out on this link for more details: http://www.codeproject.com/Tips/827339/Virtual-Cache.