为什么我们需要在 ConnectionString 中设置 Min pool size

Why do we need to set Min pool size in ConnectionString(为什么我们需要在 ConnectionString 中设置 Min pool size)
本文介绍了为什么我们需要在 ConnectionString 中设置 Min pool size的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

对于 SQL 连接池,为什么我们需要设置最小池大小?由于连接将保存在连接池中并重复使用,为什么我们需要保持最小池大小指定的活动连接?谢谢.

For SQL connection pool, why do we need to set up a min pool size? As connections will be saved in the connection pool and reused, why do we need to keep live connections specified by the min pool size? Thanks.

推荐答案

打开和维护连接很昂贵,所以如果你知道你需要多个连接(总是)最好指定 MinPoolSize 因为然后确保这些连接可用.

Opening and maintaining connections is expensive, so if you know that you need multiple connections (always) it's better to specify the MinPoolSize because then it's ensured that these connections are available.

另外,来自 MSDN:

如果 MinPoolSize 未在连接字符串中指定或指定为零,池中的连接将在一个不活动的时期.但是,如果指定的 MinPoolSize 更大大于零,连接池 直到 AppDomain 被销毁卸载并且进程结束.维护非活动或空池涉及最小的系统开销.

If MinPoolSize is either not specified in the connection string or is specified as zero, the connections in the pool will be closed after a period of inactivity. However, if the specified MinPoolSize is greater than zero, the connection pool is not destroyed until the AppDomain is unloaded and the process ends. Maintenance of inactive or empty pools involves minimal system overhead.

这篇关于为什么我们需要在 ConnectionString 中设置 Min pool size的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

DispatcherQueue null when trying to update Ui property in ViewModel(尝试更新ViewModel中的Ui属性时DispatcherQueue为空)
Drawing over all windows on multiple monitors(在多个监视器上绘制所有窗口)
Programmatically show the desktop(以编程方式显示桌面)
c# Generic Setlt;Tgt; implementation to access objects by type(按类型访问对象的C#泛型集实现)
InvalidOperationException When using Context Injection in ASP.Net Core(在ASP.NET核心中使用上下文注入时发生InvalidOperationException)
LINQ many-to-many relationship, how to write a correct WHERE clause?(LINQ多对多关系,如何写一个正确的WHERE子句?)