Pros and cons of session multiplexing
Thanks for the reply.
If you can share more details on what does the application benefit from starting a new session on the same physical connection versus starting a new physical connection? I understand that you already mentioned the credential validation and privileges check but it would be good if you could share any links which provide the list of operations which oracle will be saved from.
Also do you see any disadvantages or side effects of having session multiplexing? (i mean from a performance point of view atleast)
Does not answer the questions I had asked.
Thanks for the link. I had already read this and from this I am not able to get answers to the questions which I had asked in my earlier post. My questions are
1. What are the operations performed when establishing a connection?
2. What are the operations performed when establishing a session on an already established physical connection?
3. Are there any disadvantages or side effects of having multiple sessions on the same connection?
For simplicity we can assume a shared server configuration.
Credential verification is done when creating a session
Quote:
Originally Posted by
vnktummala
It sounds like a shared server model in Oracle. Instead of creating one physical connection for one session, session will be directed to the already established physical connection. By this way, Oracle need not do credential verification, privileges etc which saves time.
Thanks,
With the OCI connection pool, I found that even if the connection requests are made for different schemas (i.e. user name/passwords) the connection pool creates a new session on the same physical connection. This would mean that credential verification and privileges etc is done while creating a session too.