Oracle:非池连接和DRCP之间的区别 [英] Oracle: Difference between non-pooled connections and DRCP

问题描述

我实际上正在阅读 Oracle-cx_Oracle 教程./p>

我遇到了非池连接和DRCP，基本上我不是DBA，所以我用google搜索但找不到任何东西.

所以有人可以帮助我了解它们是什么以及它们之间的不同之处.

谢谢.

解决方案

Web层和中间层应用程序通常具有许多执行线程，这些线程轮流使用RDBMS资源.当前，多线程应用程序可以有效地共享与数据库的连接，从而实现出色的中间层可伸缩性.从Oracle 11g开始，应用程序开发人员和管理员以及DBA可以使用数据库驻留连接池，通过在跨中间层系统的多进程和多线程应用程序之间共享连接来实现这种可伸缩性.

DRCP 在数据库服务器中为典型的Web应用程序使用情况提供了一个连接池，在这种情况下，应用程序获取数据库连接，在相对较短的时间内对其进行处理，然后释放它.DRCP池专用"服务器.池化服务器等效于服务器前台进程和数据库会话的组合.

DRCP补充了中间层连接池，该中间池在中间层进程中共享线程之间的连接.此外，DRCP支持在同一中间层主机上甚至中间层主机之间的中间层进程之间共享数据库连接.这大大减少了支持大量客户端连接所需的关键数据库资源，从而减少了数据库层的内存占用并提高了中间层和数据库层的可伸缩性.拥有随时可用的服务器池还具有减少创建和断开客户端连接的成本的额外好处.

DRCP与具有无法执行中间层连接池的多进程单线程应用程序服务器(例如 PHP/Apache )的体系结构特别相关.数据库仍然可以扩展到与DRCP的数以万计的同时连接.

I am actually reading Oracle-cx_Oracle tutorial.

There I came across non-pooled connections and DRCP, Basically I am not a DBA so I searched with google but couldn't found any thing.

So could somebody help me understand what are they and how they are different to each other.

Thank you.

解决方案

Web tier and mid-tier applications typically have many threads of execution, which take turns using RDBMS resources. Currently, multi-threaded applications can share connections to the database efficiently, allowing great mid-tier scalability. Starting with Oracle 11g, application developers and administrators and DBAs can use Database Resident Connection Pooling to achieve such scalability by sharing connections among multi-process as well as multi-threaded applications that can span across mid-tier systems.

DRCP provides a connection pool in the database server for typical Web application usage scenarios where the application acquires a database connection, works on it for a relatively short duration, and then releases it. DRCP pools "dedicated" servers. A pooled server is the equivalent of a server foreground process and a database session combined.

DRCP complements middle-tier connection pools that share connections between threads in a middle-tier process. In addition, DRCP enables sharing of database connections across middle-tier processes on the same middle-tier host and even across middle-tier hosts. This results in significant reduction in key database resources needed to support a large number of client connections, thereby reducing the database tier memory footprint and boosting the scalability of both middle-tier and database tiers. Having a pool of readily available servers also has the additional benefit of reducing the cost of creating and tearing down client connections.

DRCP is especially relevant for architectures with multi-process single threaded application servers (such as PHP/Apache) that cannot perform middle-tier connection pooling. The database can still scale to tens of thousands of simultaneous connections with DRCP.

这篇关于Oracle:非池连接和DRCP之间的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！