| View previous topic :: View next topic |
| Author |
Message |
amiatrome
Apprentice
Joined: 28 Jun 2004
Posts: 180
Location: Campus | Arena Country Club | Home
|
 Posted: Sun Dec 05, 2004 6:59 am Post subject: High CPU Usage [solved] |
 |
|
I will try to keep it short.
I use btdownloadcurses.py of BitTornado. My ISP throttles ports 6881-6885 and so I switched to 60001-60005 recently.
Now,
1. when I use linblock and iptables to implement a HUGE blocklist, my whole system suffers. The mouse becomes sticky etc. My CPU usage is a just a little higher than last time. ~10%
2. I do an iptables -F and the entire system goes back to normal. But my CPU usage escalates even more to insane levels(it could be due to the large number of peers I am getting for this particular torrent and my choice of ports). This is impotant since torrent take time to complete and I dont wanna overwork my CPU needlessly for the entire time.
Any stabs at what's going on? Does it have anything to do with me using dynamic ports? Oh, the name of the show is really called Guess.
| Code: | | file: Guess-2004.12.04.rmvb |
| size: 304,423,251 (290 MiB) |
| dest: /mnt/main/bittorrent/Guess-2004.12.04.rmvb |
| progress: #############################################_____________________ |
| status: finishing in 0:28:21 (68.8%) |
| dl speed: 119.0 KB/s |
| ul speed: 5.1 KB/s |
| sharing: 0.167 (7.9 MB up / 47.5 MB down) |
| seeds: [b]232[/b] seen now, plus 148.999 distributed copies |
| peers: [b]766[/b] seen now, 37.9% done at 5712.9 kB/s |
| Code: | top - 14:57:22 up 13:21, 7 users, load average: 1.31, 1.41, 1.29
Tasks: 89 total, 3 running, 85 sleeping, 0 stopped, 1 zombie
Cpu(s): [b]94.7%[/b] us, 4.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 1.0% hi, 0.0% si
Mem: 514860k total, 509684k used, 5176k free, 1228k buffers
Swap: 500464k total, 404k used, 500060k free, 235152k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15634 arnold 25 0 58324 54m 4292 R [b]89.3[/b] 10.8 12:23.65 btdownloadcurse
15520 arnold 15 0 30228 27m 4292 S 7.3 5.4 3:52.63 btdownloadcurse
|
_________________
blog | homepage | alias | prompts
Last edited by amiatrome on Wed Dec 15, 2004 4:47 am; edited 1 time in total |
|
| Back to top |
|
 |
amiatrome
Apprentice
Joined: 28 Jun 2004
Posts: 180
Location: Campus | Arena Country Club | Home
|
| Posted: Wed Dec 15, 2004 4:44 am Post subject: |
|
|
Long overdue update.
I still never found the reason to the queer problem above since they occured only after a change of listening port numbers.
The previous CPU usage wasnt so high so i left Linblock to filter every packet. But after facing the problem above, I did the following to alleviate the CPU usage.
| Quote: |
By default, filtering occurs against every packet sent and received. This is the "cautious default" because some people are not using iptables in a "stateful" mode. However, most people do load the ip_conntrack module which maintains state of all the connections. If this applies in your situation, you can reduce the filtering load significantly by only filtering packets in the NEW and RELATED states. The following command can be used after running the script to do this.
iptables -R INPUT 1 -m state --state NEW,RELATED -j antip2p |
_________________
blog | homepage | alias | prompts |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
