blocks|key|5255988|text|它们都是非常可靠的项目。如果您有非常基本的缓存需求，那么它们中的任何一个都可能与另一个一样好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5255989|如果可行，您可能还希望考虑在数据库查询中进行过滤。通常，与将500,000行加载到内存中然后过滤它们相比，使用返回较小结果集的优化查询可以提供更好的性能。|5255990|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

They're both pretty solid projects. If you have pretty basic caching needs, either one of them will probably work as well as the other.

You may also wish to consider doing the filtering in a database query if it's feasible. Often, using a tuned query that returns a smaller result set will give you better performance than loading 500,000 rows into memory and then filtering them.

blocks|key|3001370|text|从他们的releases+page判断，OSCache自2007年以来就没有积极维护过。这不是一件好事。另一方面，EhCache正在不断开发中。仅仅因为这个原因，我就会选择EhCache。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3001371|2013年11月编辑:像OpenSymphony的其他部分一样，OSCache已经死了。|3001372|entityMap|0|LINK|mutability|MUTABLE|url|http://www.opensymphony.com/oscache/download.action^0|4|D|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Judging by their <a href="http://www.opensymphony.com/oscache/download.action" rel="noreferrer">releases page</a>, OSCache has not been actively maintained since 2007. This is not a good thing. EhCache, on the other hand, is under constant development. For that reason alone, I would choose EhCache.

Edit Nov 2013: OSCache, like the rest of OpenSymphony, is dead.

blocks|key|3845188|text|我使用过JCS+(http://jakarta.apache.org/jcs/)，它看起来很可靠，易于编程使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3845189|entityMap|0|LINK|mutability|MUTABLE|url|http://jakarta.apache.org/jcs/^0|9|U|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]]]]

I've used JCS (<a href="http://jakarta.apache.org/jcs/" rel="noreferrer">http://jakarta.apache.org/jcs/</a>) and it seems solid and easy to use programatically.

blocks|key|5256046|text|这在某种程度上取决于你的需求。如果您在一台机器上的内存中执行这项工作，那么ehcache将完美地工作，假设您有足够的RAM或足够快的硬盘，以便溢出不会导致磁盘分页/抖动。如果您发现需要实现可伸缩性，即使这种特定的操作经常发生，那么您可能会想要进行集群。来自JBoss的JGroups+/TreeCache支持这一点，EHcache也是如此(我认为)，而且我知道如果你将Ehcache与terracotta结合使用，这是一个非常巧妙的集成。这个答案并没有直接说明EHcache和OSCache的优点，所以答案是这样的:+EHcache似乎有最大的惯性(过去是默认的、众所周知的、活跃的开发，包括新的缓存服务器)，而OSCache似乎(至少在某一点上)有稍微多一点的特性，但我认为有了上面提到的选项，这些优点就没有意义/被取代了。啊，我忘了提到的另一件事是，数据的事务性很重要，您的需求将完善有效选择的列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5256047|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|$]]

It sort of depends on your needs. If you're doing the work in memory on one machine, then ehcache will work perfectly, assuming you have enough RAM or a fast enough hard disk so that the overflow doesn't cause disk paging/thrashing. if you find you need to achieve scalability, even despite this particular operation happening a lot, then you'll probably want to do clustering. JGroups /TreeCache from JBoss support this, so does EHcache (I think), and I know it definitely works if you use Ehcache with terracotta, which is a very slick integration. This answer doesn't speak directly to the merits of EHcache and OSCache, so here's that answer: EHcache seems to have the most inertia (used to be the default, well known, active development, including a new cache server), and OSCache seemed (at least at one point) to have slightly more features, but I think that with the options mentioned above those advantages are moot/superseded. Ah, the other thing I forgot to mention is that transactionality of the data is important, and your requirements will refine the list of valid choices.

blocks|key|3001444|text|选择一个符合JSR107的缓存，当您想要从一个实现迁移到另一个实现时，这将使您的工作变得容易。具体来说，选择Ehcache，这是一种更流行、使用更广泛的Java缓存解决方案。我们正在广泛地使用Ehcache，它对我们很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3001445|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|$]]

Choose a cache which complies to JSR 107 which will make your job easy when you want to migrate from one implementation to the other. To be specific on the question go for Ehcache which is more popular and widely used Java caching solution. We are using Ehcache extensively and it works for us.

blocks|key|3845294|text|其他答案讨论了缓存的优缺点；但我想知道您是否真的从缓存中受益。不太清楚您计划在这里做什么，以及为什么使用缓存会有好处:如果您有自己使用的数据集，只需访问它。缓存只帮助在其他独立的任务之间重用内容。如果这就是您正在做的事情，是的，缓存可以提供帮助。但如果这是一项可以承载其数据集的大任务，缓存将不会增加任何价值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3845295|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|$]]

Other answers discuss pros/cons for caches; but I am wondering whether you actually benefit from cache at all. It is not quite clear exactly what you plan on doing here, and why a cache would be beneficial: if you have the data set at your use, just access that. Cache only helps reuse things between otherwise independent tasks. If this is what you are doing, yes, caching can help. But if it is a big task that can carry along its data set, caching would add no value.

blocks|key|5256122|text|无论哪种方式，我都建议将它们与Spring模块一起使用。缓存对应用程序是透明的，并且缓存实现很容易交换。除了OSCache和EHCache，Spring模块还支持Gigaspaces和JBoss缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5256123|至于比较……OSCache更易于配置EHCache有更多的配置选项|5256124|它们都是坚如磐石的，都支持镜像缓存，都可以与Terracotta协同工作，都支持内存和磁盘缓存。|5256125|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Either way, I recommend using them with Spring Modules.
The cache can be transparent to the application, and cache implementations are trivially easy to swap.
In addition to OSCache and EHCache, Spring Modules also support Gigaspaces and JBoss cache.

As to comparisons....
OSCache is easier to configure
EHCache has more configuration options

They are both rock solid, both support mirroring cache, both work with Terracotta, both support in-memory and to-disk caching.

blocks|key|5256265|text|我已经在几个spring项目中使用了oscache，使用了基于aop的配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5256266|最近，我希望在Spring3.x项目中使用oscache+%2B+spring模块，但发现基于spring-modules注解的缓存不受支持(甚至fork也不支持)。|5256267|我最近发现了这个项目-|5256268|http://code.google.com/p/ehcache-spring-annotations/|offset|length|5256269|它使用ehcache支持Spring3.x和基于声明注解的缓存。|5256270|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|1G|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$H|W|I|X|1|Y]]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|G]]]]

I have used oscache on several spring projects with spring-modules, using the aop based configuration. 

Recently I looked to use oscache + spring modules on a Spring 3.x project, but found spring-modules annotation-based caching is not supported (even by the fork).

I recently found out about this project - 

<a href="http://code.google.com/p/ehcache-spring-annotations/" rel="nofollow noreferrer">http://code.google.com/p/ehcache-spring-annotations/</a>

Which supports spring 3.x with declarative annotation-based caching using ehcache.

blocks|key|5255963|text|我主要使用EhCache，因为它曾经是Hibernate的默认缓存提供程序。在Java-Source.net上有一个缓存解决方案列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5255964|我曾经有一个比较主要缓存解决方案的链接。如果我找到了，我会更新这个答案。|5255965|entityMap|0|LINK|mutability|MUTABLE|url|http://java-source.net/open-source/cache-solutions^0|13|F|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I mainly use EhCache because it used to be the default cache provider for Hibernate. There is a list of caching solutions on <a href="http://java-source.net/open-source/cache-solutions" rel="nofollow noreferrer">Java-Source.net</a>.

I used to have a link that compared the main caching solutions. If I find it I will update this answer.

blocks|key|756850|text|OSCache几乎已经死了，因为它在几年前就被废弃了。你可以看看Cacheonix，它已经得到了积极的开发，我们刚刚发布了2.2.2版本，支持web层的缓存。我是一个提交者，所以如果你有任何问题可以联系我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|756851|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|$]]

OSCache is pretty much dead as it has been abandoned a few years ago. You may take a look at Cacheonix, it's been actively developed and we've just released v.2.2.2 with support for caching in the web tier. I'm a committer so you can reach out if you have any questions.

Never used a cache like this before. The problem is that I want to load 500,000 + records out of a database and do some selecting/filtering wicked fast.

I'm thinking about using a cache, and preliminarily found <a href="http://ehcache.org/" rel="noreferrer">EHCache</a> and <a href="https://java.net/projects/oscache/" rel="noreferrer">OSCache</a>, any opinions?

OSCache vs. EHCache

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

以前从未使用过这样的缓存。问题是，我想要从数据库中加载500,000多条记录，并快速地进行一些选择/过滤。我正在考虑使用缓存，并且初步找到了和，你有什么意见吗？

问OSCache与EHCache
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OSCache与EHCacheEN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OSCache与EHCache
EN