为什么与数据库服务器建立连接被认为是一个繁重且高资源消耗的过程？
我们如何衡量“高资源消耗”部分？
作为后续，我还有另一个问题 -
是否为网络场中的 Web 应用程序启用了池化？泳池的尺寸是多少？
如果场中有 4 台服务器，是否会创建 4 个池？是否为每个不同的进程、应用程序域和连接字符串维护一个单独的连接池？
有没有一篇全面的文章可以解释 ADO.NET 中的连接池。我已经读过 codeproject、4guysfromrolla、google 等上的一篇，但找不到我的问题的答案。我正在寻找更全面的东西。
EF4.1 中如何处理连接池？
How do we measure the 'high resource consuming' part?
As a follow up, I have another question-
If pooling is enabled for a web application that is in a web farm? What is the size of the pool?
Are 4 pools created if there are 4 servers in the farm? Is a separate connection pool maintained for every distinct process, app domain and connection string?
Is there a comprehensive article that can explain the connection pooling in ADO.NET. I have already read the one on codeproject, 4guysfromrolla, google, etc., but could not find answers to my questions. I am looking for something more comprehensive.
How is Connection pooling handled in EF4.1?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
回答标题中提出的原始问题...
RDBMS 无非是消费的远程接口
应用程序，无论其目的如何（存储数据），以及烟雾和镜子（数据访问框架
像 O/RM）隐藏了局部性的缺乏。实际上，集成 RDBMS 的面向对象系统是一个
类似于具有 Web 服务集成的面向对象系统：存在显式远程边界并且
不能打折。感知到的、妖魔化的阻抗不匹配是
对分布式系统的误解。沙子中存在一条看不见且经常被滥用的线（远程
接口），并且当交叉时，会在 CPU 和 I/O 成本方面产生重大损失。
请参阅：http://www.softwareishardwork.com/Exusing%20the%20True%20Nature%20of%20Impedance%20Mismatches%20in%20Data%20Programming%20Models%20%5BBullington，%20D.%202010%5D。 pdf
Answer to original question posed in the title...
A RDBMS is nothing more than a remote interface to the consuming
application, regardless of its purpose (to store data), and the smoke and mirrors (data access frameworks
like O/RM) hide the lack of locality. In reality, an object oriented system with RDBMS integration is a
similar to an object oriented system with web service integration: explicit remote boundaries exist and
cannot be discounted. The perceived, demonized impedance mismatches are a symptom of the
misconception of distributed systems. An invisible and often abused line in the sand exists (remote
interface), and when crossed, incurs a significant penalty in terms of CPU and I/O cost.
See: http://www.softwareishardwork.com/Exposing%20the%20True%20Nature%20of%20Impedance%20Mismatches%20in%20Data%20Programming%20Models%20%5BBullington,%20D.%202010%5D.pdf