调整GC策略支持高并发

那你说的第四种 是不是对大对象较多的应用回收的比较好啊。收起

回复 6# 暗黑城堡new


    IBM机器有自己的回收，用第四种是最好的；收起

除了ibm的机器 啥意思 那ibm的机器用这个不好吗？收起

回复 3# wudan


    言之有理收起

gencon方式，是除了IBM机器外使用最好的回收方式；这个我们的项目都有验证，仅供您参考收起

使用哪种GC策略与特定的应用、访问场景等相关，没有一个fit-for-all的答案，需要通过性能测试来寻求答案。通常，如果是高并发、短平快的访问模式，推荐先尝试gencon策略，这也是was v8.5的默认策略，另外也可以试试 optthruput, optavgpause 等策略。收起

如果属于那种瞬间创建大量对象而后抛弃成为垃圾对象的应用，推荐使用gencon 垃圾回收模式
每一种GC策略使用场景的描述，请参考如下说明：（由于时间问题，就直接粘贴英文了）

What is the difference between the GC policies gencon, optavgpause, subpool,
and optthruput?

optthruput disables concurrent mark. If you do not have pause time problems
(indicated by erratic application response times), you can expect to get the best
throughput with this option.


optavgpause enables concurrent mark. If you have problems with erratic
application response times in garbage collection, you can alleviate them at the
cost of some throughput when running with this option.


gencon requests the combined use of concurrent and generational GC to help
minimize the time that is spent in any garbage collection pause.


subpool disables concurrent mark but employs an object allocation algorithm
that is more suitable for multiple processor systems, commonly 16 processors
or more. Applications that must scale on large systems can benefit from this
policy. This policy is available on AIX, Linux PPC and zSeries, z/OS, and
i5/OS only.收起