In the previous chapter, I talked a lot about Fiddler. In fact, there are many detection tools available, such as fiddler, chrome, firebug, network monitor, IIS and some third-party services.
First, let's continue to review the functions of Fiddler.
[Fiddler]
[Chrome browser]
Chrome is a browser developed by Google that is very suitable for developers. It can also measure the performance of a website,
Now a Chrome browser, and press F12. You can see many developer options. We can see the following tools:
Let's try what they can do. The features may pass through, because this section only focuses on performance-related features.
Element: Let's see which HTML elements are contained on the current page.
Resources: resources to reference.
Network and timeline: functions are similar to Fiddler. Is about HTTP request, response, and timeline
Profiles: Three profiles can be collected. For example, how much CPU does JavaScript occupy. You can try it yourself.
Audits is even cooler. It can provide optimization suggestions for your site. Like. He provides some suggestions. Enable gzip compression and use the browser cache to Remove unused CSS references. This page is used when I write a blog. Therefore, our yard can also improve performance :)
[Firebug]
Due to the limited space, I will not detail it here, and its functions are similar to those of chrome. Download a Firefox browser and install the firebug plug-in. Outbound call is also F12 (reminds me of the legend of plug-ins when I was a child ..)
With a diagram:
Microsoft Network Monitor]
- A common network Tracing Tool for multiple protocols. HTTP, TCP/IP, and so on.
- Network Adapter hook.
- View the network structure at multiple levels.
- Apply different filters to specific protocols, IP addresses, and other applications.
Here is the address for getting this free tool: http://www.microsoft.com/en-us/download/details.aspx? Id = 4865
If you see this, download it and try it.
First, create a new capture in the "Capture-" toolbar. Click Start in the green triangle above. Switch to IE browser. Access www.microsoft.com. Switch back and click STOP.
We can find a lot of information. Contains many protocols. Now we add a filter: HTTP
The first message is actually Sohu mail. It doesn't matter. It must have regularly sent HTTP requests to get mail information.
We can see the actual location access ***/mail/check. Yes, we are right. It is to check the email.
I just want to introduce myself here. If you are interested in Microsoft Network Monitor. See http://en.wikipedia.org/wiki/Microsoft_Network_Monitor
[IIS log file]
IIS provides two feature features for performance measurement:
- Time used
- Log Analysis
- Common methods to query IIS log files and Event Logs
- The query syntax is very similar to the SQL statement.
- Record site health information
Time used
We can use IIS log files for our performance analysis. Start IIS> selected site> Logging)
Click Select field. Select the time and fields you are interested in.
Click "OK". Each time a request comes to your IIS server. IIS will record a detailed log for you.
Log Analysis
Logparser is a command line tool that analyzes and collects logs using SQL statements. You can analyze IIS logs, System Event Logs, CSV, XML, and other format logs.
The basic usage is as follows:
Logparser-I: Format of the input file-O: output format "SQL statement"
For example, the following example uses log parser to count the IP addresses that access the entire IIS Site the most frequently:
logparser.exe -i:IISW3C SELECT TOP 25 cs-uri-stem as Url, COUNT(*) As Hits FROM c:\inetpub\logs\LogFiles\W3SVC1\* GROUP BY cs-uri-stem ORDER By Hits DESC
If you are interested in logparser. Can read this article again: http://blogs.msdn.com/ B /carlosag/archive/2010/03/25/analyze-your-iis-log-files-favorite-log-parser-queries.aspx
[Third-party services]
Keynote http://www.keynote.com/, Gomez (charged)
- Provides performance analysis services.
- Allows us to compare the performance differences between ourselves and other sites
- Provide proxy service
- Response time and validity every X minutes.
Thank you for reading this article. In the next chapter, we will introduce [infrastructure performance ].