How Can I Resolve High Bandwidth Usage on My ECSs?
Scenarios
If an ECS responds slowly or even cannot be accessed, this issue may be caused by high bandwidth usage.
Windows ECS
- Remotely log in to the ECS on the management console.
- Start the Run dialog box, and then enter perfmon -res.
Figure 1 Starting the Resource Monitor
- On the Resource Monitor page, click the CPU or Network tab to view the CPU or bandwidth usage.
- View the processes with high bandwidth usage.
- If such processes are service processes, you are advised to modify ECS specifications.
- If such processes are abnormal ones, they may be caused by viruses or Trojan horses. You are advised to stop the processes or use security software to scan for and stop them.
Linux ECS
- Log in to the ECS through the management console.
The following uses an ECS running CentOS 6.8 64bit as an example.
- Run the following command to install the Linux traffic monitoring tool iftop:
- Run the following command to check the ports that cause heavy traffic and the IP addresses that consume high bandwidth (taking port eth0 as an example):
iftop -i eth0 -P
- Run the following command to check the processes related to the port (taking port 38366 as an example):
netstat -tunlp |grep 38366
- => indicates transmitted data, and <= indicates received data.
- TX indicates TX traffic, RX indicates RX traffic, and TOTAL indicates the total traffic.
- cum indicates the total traffic in the first column.
- peak indicates the peak traffic in the first column.
- rates indicates the average traffic within 2, 10, and 40 seconds in the first column.
- View the processes with high bandwidth usage.
- If such processes are service processes, you are advised to modify ECS specifications.
- If such processes are abnormal ones, they may be caused by viruses or Trojan horses. You are advised to stop the processes or use security software to scan for and stop them.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.