oracle 最多可以有多少个连接？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/1648752/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
How many maximum connections can oracle have?
提问by Puzzled
How many maximum number of connections can oracle handle ?
oracle 最多可以处理多少个连接？
The following is a summary for my sql, i need similar stats for oracle :
以下是我的 sql 的摘要，我需要类似的 oracle 统计信息：
The maximum number of connections MySQL can support depends on the quality of the thread library on a given platform, the amount of RAM available, how much RAM is used for each connection, the workload from each connection, and the desired response time. Linux or Solaris should be able to support at 500–1000 simultaneous connections routinely and as many as 10,000 connections if you have many gigabytes of RAM available and the workload from each is low or the response time target undemanding. Windows is limited to (open tables × 2 + open connections) < 2048 due to the Posix compatibility layer used on that platform.
MySQL 可以支持的最大连接数取决于给定平台上线程库的质量、可用 RAM 量、每个连接使用多少 RAM、每个连接的工作负载以及所需的响应时间。Linux 或 Solaris 应该能够定期支持 500-1000 个同时连接，如果您有许多 GB 的可用 RAM 并且每个连接的工作负载很低或响应时间目标不高，则可以支持多达 10,000 个连接。由于该平台上使用的 Posix 兼容层，Windows 仅限于（打开表 × 2 + 打开连接）< 2048。
回答by Vincent Malgrat
Oracle has two types of connection architecture:
Oracle 有两种类型的连接架构：
- In dedicated servermode, each connection has a server process and you should have roughly the same limitations as in MySQL. This is the default connection mode and is recommended for small setup.
- In shared servermode the connections will share the server processes:
Shared serverarchitecture eliminates the need for a dedicated server process for each connection. A dispatcher directs multiple incoming network session requests to a pool of shared server processes. An idle shared server process from a shared pool of server processes picks up a request from a common queue, which means a small number of shared servers can perform the same amount of processing as many dedicated servers. Also, because the amount of memory required for each user is relatively small, less memory and process management are required, and more users can be supported.
共享服务器架构消除了对每个连接的专用服务器进程的需要。调度程序将多个传入的网络会话请求定向到共享服务器进程池。来自共享服务器进程池的空闲共享服务器进程从公共队列中获取请求，这意味着少量共享服务器可以执行与许多专用服务器相同的处理量。并且由于每个用户需要的内存量比较小，所以需要的内存和进程管理更少，可以支持更多的用户。
The jump from dedicated server to shared server architecture will be dictated by the number of connections and the workload. A mix of the two is possible (long running batch jobs in dedicated, front end web application in shared architecture).
从专用服务器到共享服务器架构的跳跃将取决于连接数量和工作负载。两者的混合是可能的（在共享架构中的专用前端 Web 应用程序中长时间运行批处理作业）。
