Why is the database connection creation Overhead High?

Why is the connection overhead large? Developers often think that creating a database is a simple requirement. Isn't it a network round-trip between the database server and the initialized user? But in fact, A database connection has multiple network trips between the driver and the database server. For example, when a driver is connected to Oracle or Sybase, the connection

Why is the connection overhead large? Developers often think that creating a database is a simple requirement. Isn't it a network round-trip between the database server and the initialized user? But in fact, A database connection has multiple network trips between the driver and the database server. For example, when a driver is connected to Oracle or Sybase, the connection

Why is the connection overhead large?

Developers often think that creating a database is a simple requirement. Isn't it a network round-trip between the database server and the initialized user? But in fact, A database connection has multiple network trips between the driver and the database server. For example, when a driver is connected to Oracle or Sybase, the connection has 7 to 10 and network connections, A series of actions are performed:

◆ Verify the user's ID card

◆ Negotiate between the desired code page setting of the database driver and the available code page setting of the database (if necessary)

◆ Obtain database version information

◆ Determine the optimal database protocol package size for communication

◆ Set session settings

In addition, database management (the best practice when developers assume the responsibilities of Database Administrators) determines the resources used to establish connections, including disk I/O and memory allocation with high performance overhead, you may think that deploying an application to a database server will eliminate network round-trips. In most cases, this is not realistic, because most enterprises in the real world will not do this, they have a lot of applications and a lot of databases. In addition, the database server will make careful performance adjustments for the database system, and generally will not make adjustments for different applications, even if you can install databases and applications on a single machine, this also has the risk of single point of failure.

From: http://database.51cto.com/art/200907/136845.htm