>>Helpful Points on .NET Performance
- Pre-size ArrayLists/Hashtables etc, the performance/memory impact of not doing this is massive if you are working with lists/tables/queues that have 1000's of items
- Build instrumentation into the codebase from the outset - you'll need it later for performance critical applications
- Analysis and understand the problem before you refactor/re-code
- Don't log too little or too much. Logging takes time. The TextWriterTraceListener classes are not thread safe. Adding a queue in front of the TextWriterTraceListener moves you into the area of point 1 above.
- .NET Remoting calls are expensive - the call and the serialization. Chunky not chatty.
- Use the PerfMon counters
文章来源:http://weblogs.asp.net/mdavey/archive/2004/02/25/79788.aspx
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】凌霞软件回馈社区,博客园 & 1Panel & Halo 联合会员上线
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】博客园社区专享云产品让利特惠,阿里云新客6.5折上折
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 一个奇形怪状的面试题:Bean中的CHM要不要加volatile?
· [.NET]调用本地 Deepseek 模型
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· .NET Core 托管堆内存泄露/CPU异常的常见思路
· PostgreSQL 和 SQL Server 在统计信息维护中的关键差异
· DeepSeek “源神”启动!「GitHub 热点速览」
· 我与微信审核的“相爱相杀”看个人小程序副业
· 微软正式发布.NET 10 Preview 1:开启下一代开发框架新篇章
· C# 集成 DeepSeek 模型实现 AI 私有化(本地部署与 API 调用教程)
· spring官宣接入deepseek,真的太香了~