Connection pool

In software engineering, a connection pool is a cache of database connections maintained so that the connections can be reused when future requests to the database are required. Connection pools are used to enhance the performance of executing commands on a database. Opening and maintaining a database connection for each user, especially requests made to a dynamic database-driven website application, is costly and wastes resources. In connection pooling, after a connection is created, it is placed in the pool and it is used again so that a new connection does not have to be established. If all the connections are being used, a new connection is made and is added to the pool. Connection pooling also cuts down on the amount of time a user must wait to establish a connection to the database.

Applications

Web-based and enterprise applications use an application server to handle connection pooling. Dynamic web pages without connection pooling open connections to database services as required and close them when the page is done servicing a particular request. Pages that use connection pooling, on the other hand, maintain open connections in a pool. When the page requires access to the database, it simply uses an existing connection from the pool, and establishes a new connection only if no pooled connections are available. This reduces the overhead associated with connecting to the database to service individual requests.

Local applications that need frequent access to databases can also benefit from connection pooling. Open connections can be maintained in local applications that don't need to service separate remote requests like application servers, but implementations of connection pooling can become complicated. A number of available libraries implement connection pooling and related SQL query pooling, simplifying the implementation of connection pools in database-intensive applications.

Administrators can configure connection pools with restrictions on the numbers of minimum connections, maximum connections and idle connections to optimize the performance of pooling in specific problem contexts and in specific environments.

Database support

Connection pooling is supported by IBM DB2,[1] Microsoft SQL Server,[2] Oracle,[3] MySQL,[4] PostgreSQL,[5] and Neo4j.[6]

gollark: I think theoretically stuff could be switched over to a non-SHA256 algorithm, requiring... either the majority of mining power to agree to it or I guess just a lot of the nodes.
gollark: A similar sort of thing probably happened when ASICs which do SHA256 much faster than GPUs do were initially used.
gollark: If SHA256 could be done much faster, that would just make whatever can do it really fast the only way to do mining; it autoadjusts to the available has hpower.
gollark: As far as I'm aware the blockchain thing itself is basically just a Merkle tree, except... well, a single chain and not really a tree.
gollark: https://bitcoin.org/bitcoin.pdf

See also

References
  1. IBM Connection Pooling Support
  2. SQL Server Connection Pooling (ADO.NET)
  3. OCI Driver Connection Pooling
  4. MySQL Connection Pooling
  5. PostgreSQL Replication, Clustering and Connection Pooling
  6. "4.2. Client applications - Chapter 4. Drivers". neo4j.com. Retrieved 2018-02-23.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.