关闭连接池的后果是什么？ [英] what are the consequences of turning off connection pooling?

问题描述

我有一个主应用程序使用ODBC驱动程序和连接池。单独的程序还通过相同的驱动程序访问连接池，但是通过此第2个程序检测到连接池和驱动程序的问题。

I have a main application using an ODBC driver and connection pooling. A separate program also accesses the connection pools via the same driver but an issue has been detected with the connection pool and driver by this 2nd program.

如果我们关闭连接池它工作正常。

If we turn off connection pooling it works fine.

如果我关闭连接池，我们可以/我们应该关闭和打开这个第二个程序运行时，主应用程序的后果是什么？

What are the consequences for the main application if I turn off connection pooling and could we / should we be turning it off and on whilst this 2nd program runs?

推荐答案

我讨厌陈述明显的，但如果你禁用连接池然后应用程序连接和断开连接不会使用池连接，每次都必须重新连接。这可能意味着受益于池的应用程序有点慢，但它取决于很多因素，例如，默认池超时是60秒，所以如果你每2分钟只连接一次，你不使用池连接。

I hate to state the obvious but if you disable the connection pool then applications connecting and disconnecting repeatedly will not use a pooled connection and will have to connect afresh each time. This may mean the application which was benefiting from the pool is a little slower but it depends on a lot of factors e.g., the default pool timeout is 60s so if you were connecting only once every 2 minutes you weren't using pooled connections anyway.

这篇关于关闭连接池的后果是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！