Yesterday morning to the company, research and development email notification that there are users to reflect the login we a station speed is very slow, log in after the operation is normal, so the basic can rule out the network and server pressure factors.
Then the next step is to see if the database and cache become a bottleneck, the result is nothing to find, after all, a station is already marginalized products, no one to maintain on weekdays.
Logon slowness is nothing more than a few reasons: database bottlenecks, caching problems, program code problems, concurrency, large application server load too high, call third-party interface.
Several other reasons can be directly discharged, then only the program code problems and calls to third-party interface these two suspicious, in order to exclude the former suspicion, I put on the test server deployed another set of environments, the code rolled back to the version of N months ago, but the problem is still. So there's only one reason left: A station invokes a third-party interface when it logs on. Can a station for a long time no maintenance, and the original developer has left, specifically to call which external interface who is not clear.
Helpless, had to log on to the server to grab the package, try to analyze whether the packet contains calls to other URLs, the result URL is not found, but unexpectedly see the problematic connection:
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/87/wKioL1P8AYbgwjw5AAMNvsER3cI304.jpg "title=" QQ picture 20140826113515.jpg "alt=" Wkiol1p8aybgwjw5aamnvser3ci304.jpg "/>
From the point of view, the connection sent to 114.112.81.104 does not return data, on the server see a station local server also just send data to this address, but no response:
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/85/wKiom1P8AObQFxPNAADCoLXLH60352.jpg "title=" QQ picture 20140826113515.jpg "alt=" wkiom1p8aobqfxpnaadcolxlh60352.jpg "/> thus concluded that When a station is logged in, it calls the 114.112.81.104 80 port (from the internal record, which can be traced to the corresponding URL according to this IP). Later found that the URL has been invalidated, inaccessible, so the login time to call the invalid URL will wait until the timeout to continue to the next step, which is the real reason for the slow logon speed.
This article is from the "Zhaohaihua _ Yun-dimensional Road" blog, please be sure to keep this source http://baiying.blog.51cto.com/1068039/1545096
One site login Slow troubleshooting