Fiddler testing for Weak Nets

fiddler The principle of analog speed limit

We can simulate the speed limit by Fiddler, because Fiddler is an agent that provides callback interfaces before and after the client's request, and we can customize some logic in these interfaces. Fiddler's analog Speed limit is the logic that defines the speed limit before the client requests it, which restricts the download speed and upload speed of the network by delaying the sending of data or receiving data, thus achieving the speed limit effect.

He provides a feature that allows us to simulate low-speed network environments ... The Enable method is as follows:

Rules→performances→simulate Modem Speeds: Analog modem speed

The following settings are required to start fiddler:

1. Set the port number:

Allow remote computers to connect "permit the connection to the computer" to set the agent can be connected to the fiddle, you must check

2. Restart the fiddle;

3. Set the speed of the analog modem:

4. Set up the phone agent

Phone proxy settings "IP address is native IP, port number is previously set port number (ensure port number is not occupied)"

5. Manually set the uplink, downlink rate, analog network speed principle, each upload/download 1KB how long to delay ...

The algorithm of network value is 1000/download speed = time of delay (milliseconds), such as 50kb/s need delay200 milliseconds to receive data.

Find the following code:

if (M_simulatemodem) {

Delay sends by 300ms per KB uploaded. Send 1kb of data per 300ms delay, i.e. 3kb per 1s

osession["Request-trickle-delay"] = 300

Delay receives by 150ms per KB downloaded.

osession["Response-trickle-delay"] = 150//1kb of data per delay 150ms downstream

}

Please note that when you archive, the original already checked Simulatemodem Speeds will be uncheck, remember to rules→performances→simulate Modem Speeds tick Oh. 6. After the setup is complete, empty the original log and use your app to operate under weak network conditions.

Select the first request and the last request to get the overall time consumed by the entire page load. You can also separate which requests take the most time from the bar chart to optimize access to the page

The following figure:

Graphical tables with varying requests, which take the most time-consuming resources and are optimized:

Figure below