< gcAllowVeryLargeObjects>元素 [英] <gcAllowVeryLargeObjects> Element

问题描述

我们正在研究在主题中启用标记，然后我的一个团队成员指出了以下文章，尽管该文章已经有8年历史了:  https://www.simple-talk.com/dotnet/net-framework/大型对象堆的危险/

We're looking at enable the flag in the subject and then one of my team members pointed out the following article albeit it is 8 years old: https://www.simple-talk.com/dotnet/net-framework/the-dangers-of-the-large-object-heap/

从那时起，我进行了任何更改或改进，因此我不必担心本文中提到的风险.

Has there been any changes or improvements since then that I don't need to worry about the risks mentioned in this article.

谢谢.

推荐答案

Cullen Tsering，

Hi Cullen Tsering,

谢谢您在这里发布.

对于您的问题，您提供的链接是8年前.如果您认为该解决方案不适合您，则可以参考以下博客.

For your question, the link you provided is 8 years ago. If you think the solution is not suitable for you, you could refer to the following blog.

https://www. simple-talk.com/dotnet/net-framework/large-object-heap-compaction-should-you-use-it/

它提供了三种避免LOH碎片化的方法.

It provide three ways to avoid the LOH fragmentation.

通常，解决LOH碎片问题需要遵循以下三种策略之一.

• 找出导致碎片的大对象，然后将其分解为较小的部分，这些小部分将被功能上等效的包装器类吸收.
• 重新构建应用程序的各个部分，以减少混乱大对象
• 定期重新启动应用程序(这实际上是回收ASP.NET应用程序的应用程序池所要实现的目标)

我希望这会有所帮助.

最好的问候，

温迪

Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. 

Microsoft does not control these sites and has not tested any software or information found on these sites; Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. 

这篇关于< gcAllowVeryLargeObjects>元素的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！