在SQL SERVER（如preSS）连接池 - 推荐量？ [英] Connection pooling in SQL SERVER (express)- recommended amount?

问题描述

在那里..，我的应用程序是使用asp.net和针对SQL EX preSS C＃相同的服务器上。来回每个应用程序我有用于连接池使用连接的推荐量

is there a recommended amount of connections fro each application i have for use with connection pooling.., my apps are using asp.net and c# against sql express on the "same" server.

我已经运行5应用程序，他们没有大量使用，所有的连接打开和关闭。

I have 5 applications running, they are not used intensively, all connections are opened and closed..

所以我想设置每个应用程序具有分池= 5

So i was thinking of setting each app to have min pool = 5

所以这个5×5 = 25

so this 5 x 5 = 25

可以在SQL EX preSS处理25连接...嗯，事实上5个游泳池和5个连接每个池？

Can sql express handle 25 connection ... well actually 5 pools and 5 connections each pool?

我可以去多达十？而是否有必要把MAX池属性的连接字符串中，以确保我不走了每个池多少？

Could i go up to ten? And is it necessary to put MAX pool property in the connection string to ensure i don't go over a number per pool?

任何帮助真的AP precaited

Any help really apprecaited

推荐答案

连接的数量确实很重要一点。你可以让连接池的大小在默认100

The number of connections does matter little. You can let the connection pool size at the default 100.

重要的是对的请求的数量。其中的SQL防爆preSS的局限在于，它只能运行一个调度< /一>，所以实际上它仅使用一个CPU内核。这限制了可以被处理的请求数量。有没有硬性限制，就是这样的一个CPU核心将能够处理只有一定量的工作，你开始注意到性能降低您的应用程序之前（请求需要较长时间才能完成）。

What matters is the number of requests. One of the limitations of SQL Express is that it only runs one scheduler, so in effect it utilizes only one CPU core. This limits the number of requests that can be processed. There is no hard limit, is just that the one CPU core will be able to handle only a certain amount of work before you start noticing performance degradation in your applications (requests take longer to complete).

的前preSS第二个重要的限制是1 GB最大缓冲区池大小。这限制了可以被缓存的数据量和该过程高速缓存的大小。其结果是较短的页面内存寿命和更高的I / O，以及计划更经常汇编。所有这些又有助于逐渐性能下降。

The second important limitation of Express is the 1 GB max buffer pool size. This limits the amount of data that can be cached and the size of the procedure cache. The result is shorter page in-memory lifetime and higher I/O, as well as more often compilations of plans. All these again contribute to gradual performance degradation.

当你使用SQL防爆preSS看有你达到没有硬性限制，并停止工作，就是这样被限制在它分配的硬件资源，其结果是一个有限的整体吞吐量。当你接近吞吐量的限制，性能开始下降。

As you see with SQL Express there is no hard limit you reach and it stops working, is just that is constrained in what hardware resources it allocates and the result is a limited overall throughput. As you approach that throughput limit, performance start to degrade.

在旧版本的MSDE有5个并发请求查询的限制，6日请求MSDE发动机会人为地放慢自行关闭。

On the older version MSDE there was a query limit of 5 concurrent requests, on the 6th requests the MSDE engine would artificially slow itself down.

这篇关于在SQL SERVER（如preSS）连接池 - 推荐量？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！