c# - How long does it take to create a new database connection to SQL -
Does anyone offer me a Ballpark timing (in milliseconds) how much time to set up a new DB connection from SQL It seems C #. To wit. When a connection pool should create a new connection, then what is an overhead.
It depends:
- Time to resolve
- TCP socket or open pipe time (at the top of other TCP soket): 3 IP packet usually
- encryption is required, then SSL / TLS Time to Swan: ~ 5 roundtrips and SSL / TLS key information are not reused (like an RSA private key access, which is very expensive) Master Key Time to bootstrap Exchange
- Time to authenticate SQL passwords for SQL authentication (2 roundtrips that I believe)
- To authenticate NTLM / Kerber for integrated athlete Time (1 round trip SPNEGO, if you have a curb ticket to negotiate with 5-6 roundtrips
- Time to authorize logins (lookup metadata, permissions against login token
- To run any login trigger at the moment possible
- The time to start the connection
A few more esoteric times:
- If the time has been set to open the self-closing database (<
- If the etchbdfile is used and the DB is not already connected then < Li> Time to attach database
- Time for user to start "For example SQL 2005 RANU This is approximately 40-60 seconds.
Usually you can make 10-15 new connections per second. If there is a problem (for example DNS lookup problem, IPsec issued, SSL problems, issue of Kerberos), then it can easily go into 10-15 seconds per connection.
On the contrary, only an existing pool connection is to be executed. Sp_resetconnection (which is a roundtrip on the current channel), and even if necessary, can be avoided.
Comments
Post a Comment