oracle最大连接数是多少?

发布于 2024-08-09 15:03:59 字数 308 浏览 3 评论 0原文

oracle 最多可以处理多少个连接?

以下是我的sql的摘要,我需要oracle的类似统计数据:

MySQL可以支持的最大连接数取决于给定平台上线程库的质量、可用的RAM量、每个连接使用了多少RAM连接、每个连接的工作负载以及所需的响应时间。 Linux 或 Solaris 通常应该能够支持 500-1000 个并发连接,如果您有许多 GB 的可用 RAM 并且每个连接的工作负载较低或者响应时间目标要求不高,则可以支持多达 10,000 个连接。 Windows 限制为(打开表 × 2 + 打开连接)< 2048 由于该平台上使用的 Posix 兼容层。

How many maximum number of connections can oracle handle ?

The following is a summary for my sql, i need similar stats for 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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

错爱 2024-08-16 15:03:59

Oracle 有两种类型的连接架构:

共享服务器架构消除了
需要专用服务器
每个连接的进程。一个
调度员指挥多个传入
网络会话请求池
共享服务器进程。闲着的
来自共享的共享服务器进程
服务器进程池拾取一个
来自公共队列的请求,其中
表示少量共享服务器
可以执行相同数量的
处理尽可能多的专用服务器。
另外,由于内存量
每个用户的需求是相对的
小,内存和进程较少
需要管理,并且更多
用户可以得到支持

从专用服务器到共享服务器架构的跳跃将取决于连接数量和工作负载。两者的混合是可能的(在共享架构中的专用前端 Web 应用程序中长时间运行批处理作业)。

Oracle has two types of connection architecture:

  • In dedicated server mode, 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 server mode the connections will share the server processes:

Shared server architecture 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).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文