Recent new deployed a database server, operating system, for windowsNT12 oracle for 11.2.4, hardware configuration for CPU * 24, memory * 128 g, network for the shuttle, deployment over a period of time after the completion of the internal test, a single client connection is normal, then switch to the production environment, with the increase of client connection, about 200 connections per second, at this time the client open every time the connect operation is close to 1 second, each test client tnsping server time from 400 to 600 milliseconds, a single client & lt; 20 milliseconds, and check the network, the real-time speed of 100 m is OK, and close the firewall, check the TNS, listening, DNS is not found the problem, why delay so much, didn't find the reason, you have to reinstall the server, switching to Linux + oracle, delay problem solving, is Windows + oracle efficiency?

CodePudding user response:

Do have the reasons,

In addition, tnsping did other aspects of the testing?

CodePudding user response:

First started testing from the network, the firewall front, rear change, at the same time the monitoring server and database load, high load production access after all did not appear, the database log and front-end log shows a connection timeout alarm respectively, suspected to be monitored or DNS configuration problem, repeatedly modify configuration, with hosts or directly with IP are tried, produces the connection, has greatly increased delay, ping directly delay does not affect it, eventually under the pressure of the production department, to give up,

CodePudding user response:

200 connections per second means: 200 per second short connection? This is too high

CodePudding user response:

reference minsic78 reply: 3/f

200 connections per second means: 200 per second short connection? This is too high

See the description of the original poster later, apparently did not mean this?
Windows and Linux is a big different, both the use of memory, but the feeling is not the operating system's problems, there may be other factors of different thread without description,

CodePudding user response:

reference minsic78 reply: 3/f

200 connections per second means: 200 per second short connection? This is too high

Really is, is a short connection methods used by the client, I also forward the modification for the connection pool way, but the problems involved in the front-end renovation work have adopted, so long connection scheme haven't tested,

CodePudding user response:

reference 4 floor minsic78 response:

Quote: reference minsic78 reply: 3/f

200 connections per second means: 200 per second short connection? This is too high

See the description of the original poster later, apparently did not mean this?
Windows and Linux is a big different, both the use of memory, but the feeling is not a problem of the operating system, there may be other factors of different thread without description,

Post description in the middle of the omitted many validation process, the beginning is suspected of network problems, firewall, DNS servers to rule out the possibility of a problem; Then wonder is short connection caused by excessive congestion, increased the maximum number of connections, adjust the timeout, increase the listener port, also did not receive the effect; Third step, according to the operation of the existing good set up another set of production base, optimize the new library, also did not play a role; Relocated to Linux system, finally had to switch later found delay phenomenon is greatly improved, so until now also didn't find out the cause of the delay is high,

CodePudding user response:

This has nothing to do with maximum number of connections, if really no way to switch to the connection pool, suggest at least turn off the default log audit: noaudit session whenever successful; , otherwise not to mention in the Shared pool contention, light sys. Aud $contention on the table will make you slow to log in, but it can't explain to you the Linux situation better, moved to Linux is the right choice, of course,