博客讨论了数据库连接池如何处理多个中间层会话的并发请求，强调了合适的连接池大小对于避免资源争抢的重要性。同时，提到了并发会话可能面临的行级锁冲突和系统资源（CPU、RAM、I/O）过载问题，以及这些问题如何影响会话性能。文章指出，Oracle数据库可以同时处理多个会话的查询，但资源竞争可能涉及不同用户会话，导致性能干扰。
Depends what you mean by "interfere".
Your middle tier connection pool will open a number of physical connections to the database. Sessions in the middle tier will request a connection from the pool, do some work, and return the connection to the pool. Assuming that your connection pool is large enough to handle the number of simultaneous calls being made from your application (based on the number of sessions, the length of time each session needs a logical connection, and the fraction of "think time" to "action time" in each session), you won't experience contention due to opening connections.
Oracle is perfectly happy to run queries in multiple sessions simultaneously. Obviously, though, there is the potential for one session to contend with another session for resources. Two sessions might contend for the same row-level lock if they are both trying to update the same row. If you have enough sessions, you might end up in a situation where CPU or RAM or I/O is being overtaxed and the load that one session creates causes performance issues in another session. Oracle doesn't care which Oracle user(s) are involved in this sort of contention-- you'd have the same potential for interference with 10 sessions all running as 1 user as you would if there were 10 sessions running as 10 different users assuming the sessions were doing the same things.
扫一扫
418
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
