CPU usage

[bamboleo]

80G Hd, 786Mb RAM, 2G processor, Pentium 4, 2.66GHz
WinMXVer 3.53
i started having problems recently with WinMX using 80% - 90% CPU.
after searching the forums i set the Search Thread Duty Cycle down to %40 and that definitely helped.
Allocated bandwidth I kept at 7Kb out and 10Kb in as recommended
Outgoing bandwidth is limited to 175,000.

So now it is down to %50 CPU and 26,356K Mem Usage.
Firefos only uses about 35% CPU but 141,032K Memory.

Also there are three svchost.exe processes
right now all are using about %0 CPU
3 have Mem usage of 3Kb - 5Kb
1 is using 31,768Kb

Anyways is %50 the general figure?

Thanks for any input

[Max™]

Hi and Welcome bamboleo,

i have heard of something simmilar to this, when winmx was started it would use 80% cpu for a couple of minutes,
this was caused by alot of incomplete files, if you have them, try deleting them,

i know some people like 100+ incomplete's in a shared folder, but winmx has to load them up each time, resorce consuming,

also check in task manager for Dr.Watson, its a debug program from microsoft, it seems to slow you down in some cases and can make a program like winmx use alot as it attempts to debug it, mainly because winmx like alot of programs, probably doesnt have a microsoft aproved certificate, and that is what Dr.Watson looks for and is so annoying and 90% useless.

[bamboleo]

yes i am guilty with about 126 incomplete files.
but if that only affects startup of WinMX i figure that is okay - or is it reloading all the time?

i had IE open to compare Task Manager specs and exited Firefox by mistake.
when i reopened it Memory Usage was at about 80,000K, so apparently after a lot of activity i should exit and restart.

[White Stripes]

trick i found that works great with apps that 'leak' (any app) ... simply logout (dont restart ... logout...) wait for the hdd to stop thrashing about and then log back in.... gives a fresh start  on all 'user' apps since it shuts them all off but leaves things like the virus scanner and firewall (if any) and of course the os itself in ram so when logging back in things much start faster than a complete reboot...

note: mxmoni and leechammer can soak up more ram with winmx so use with care...

another trick for mx; use the task manager to set winmxs' process priority to 'below normal' this will reduce the chance that it will cause possible lockups due to too much memory allocation... but this will cause problems with primary connections (the secondaries connected to you will suffer causing an overall bad experence) so if you use this trick make sure to connect secondary...

i used to have around 200+ incomplete files at one time so i know what you are going through

[bamboleo]

ok
now i have cable and use a primary connection which i understand helps out the overall community.
i could try your suggestion and change it back later.

the Mem usage is low it is just the CPU usage which i do not know if it is normal.
right now i have only two uploads, no downloads happening and and CPU usage fluctuates from 30% - 50%

also i found this about FF:
http://cybernetnews.com/this-may-help-your-firefox-memory-leak/

looks like making after making this change then by minimizing FF then maximizing the memory will be released.
but i have not tried it yet.

[White Stripes]

you could also be getting ddosed .... run a program from sysinternals.com called tcpview.... if you have an inordanate amount of connections from the ip ranges in this list; https://www.winmxworld.com/files/block_list.txt (the 'mediadefender' ones might be the biggest offenders) then thats likely where the memory is going....

...unfortunatly if this is the case i do not have the proper/full advice on how to deal with it... but if that is the problem pls say so and those experenced with this situation might be able to help (ghostship? you out there?)

[bamboleo]

nothing on the list showed up.
here is what i got if anyone can read it.

[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1207   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1203   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1219   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1212   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1220   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1200   a96-17-147-122.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1196   207.46.16.252:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1214   a96-17-75-122.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1205   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1206   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1218   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1202   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1194   207.46.16.252:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1223   a96-17-146-51.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1211   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1199   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1208   64.4.30.89:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1204   a96-17-147-115.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1209   a96-17-146-51.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1217   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1213   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1197   207.46.16.252:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1198   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
[System Process]:0   TCP   owner-83090dd84.hsd1.fl.comcast.net.:1210   a96-17-147-97.deploy.akamaitechnologies.com:http   TIME_WAIT   
alg.exe:704   TCP   owner-83090dd84:1026   owner-83090dd84:0   LISTENING   
firefox.exe:1464   TCP   owner-83090dd84:4307   localhost:4306   ESTABLISHED   
firefox.exe:1464   TCP   owner-83090dd84:4306   localhost:4307   ESTABLISHED   
firefox.exe:1464   TCP   owner-83090dd84:4304   localhost:4305   ESTABLISHED   
firefox.exe:1464   TCP   owner-83090dd84:4305   localhost:4304   ESTABLISHED   
lsass.exe:824   UDP   owner-83090dd84:isakmp   *:*      
lsass.exe:824   UDP   owner-83090dd84:4500   *:*      
svchost.exe:1056   TCP   owner-83090dd84:epmap   owner-83090dd84:0   LISTENING   
System:4   TCP   owner-83090dd84:microsoft-ds   owner-83090dd84:0   LISTENING   
System:4   TCP   owner-83090dd84.hsd1.fl.comcast.net.:netbios-ssn   owner-83090dd84:0   LISTENING   
System:4   UDP   owner-83090dd84.hsd1.fl.comcast.net.:netbios-ns   *:*      
System:4   UDP   owner-83090dd84.hsd1.fl.comcast.net.:netbios-dgm   *:*      
System:4   UDP   owner-83090dd84:microsoft-ds   *:*      
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   pppax355.osaka-ip.dti.ne.jp:4517   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   w7d52.bn24.vectant.ne.jp:10531   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   p15142-ipngn100101sizuokaden.shizuoka.ocn.ne.jp:2608   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   p2239-ipbfp305osakakita.osaka.ocn.ne.jp:19036   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:3515   zaqdb73f22c.zaq.ne.jp:6699   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   va-71-48-137-98.dhcp.embarqhsd.net:23188   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   p4bc7fe.osaknt01.ap.so-net.ne.jp:2329   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   93-43-166-55.ip92.fastwebnet.it:54537   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:3518   cpe-72-225-171-118.nyc.res.rr.com:6699   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   khp059140029136.ppp-bb.dion.ne.jp:1503   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   den-69-171-160-51.evdo.leapwireless.net:3995   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   kd113157143126.ppp-bb.dion.ne.jp:1131   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:4723   143.156.197.113.dy.bbexcite.jp:6699   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   cpe001cf04365d3-cm0012c90ce4b8.cpe.net.cable.rogers.com:1901   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   p9228-ipngn801funabasi.chiba.ocn.ne.jp:1375   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   119-230-95-218.eonet.ne.jp:1062   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   92.26.163.127:15245   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84.hsd1.fl.comcast.net.:6699   softbank220006250006.bbtec.net:1087   ESTABLISHED   
WinMX.exe:3888   TCP   owner-83090dd84:6699   owner-83090dd84:0   LISTENING   
WinMX.exe:3888   UDP   owner-83090dd84:6257   *:*      
WinMX.exe:3888   UDP   owner-83090dd84:3511   *:*      

[Joshua203]

...unfortunatly if this is the case i do not have the proper/full advice on how to deal with it...

if this is the case i ld say ..try blocking them at router level ...that is..if your router offers a controlable firewall
simply add the blocklist ip's (or ranges) and this should give some peace

[Joshua203]

hit the button to view IP numbers banboleo

[White Stripes]

@Joshua; problem with blocking them like that is whatever is blocking it is going to be the overloaded part of the network... so i didnt really want to anything that could possibly make things worse...

like adding the IPs to a software firewall would put the cpu load and ram use on the firewall but take it off MX... and im not sure which way is the best way to go... but looking at the list i dont think DDoS by mediadefender is the problem....

[GhostShip]

Akaimai Technology is a server supplier to MSN/Microsoft live, those can be safely ignored, the rest seem to be run of the mill IP's from Japan, nothing stands out as troublesome out of the list however Its not clear from the list you have shown whether your receiving a microsoft update in the background since you have more than one "system 4" item in the list.

[Joshua203]

@Joshua; problem with blocking them like that is whatever is blocking it is going to be the overloaded part of the network... so i didnt really want to anything that could possibly make things worse...

like adding the IPs to a software firewall would put the cpu load and ram use on the firewall but take it off MX... and im not sure which way is the best way to go... but looking at the list i dont think DDoS by mediadefender is the problem....

well sure i could be wrong, but since a firewall is designed to do just that i would prefer to stop traffic at the verry edge of  my network rather than letting it go in all the way to the winmx patch feature (blocking) wich is only a addon in the patch

again ..i could be verry well wrong Stripes 

[GhostShip]

As the community patch is not blocking any of those IPs its hard to understand why anyone would believe they are the cause of this problem

[White Stripes]

chat list grab ddos is what was the first thing that came to my mind... (i guess they gave up on that?)

[White Stripes]

PS akami is a bandwidth provider for a very large amount of companies all over the globe... not just MS...

[Max™]

I have seen this myself 100's or even 1,000's of connections in the wait status ,
most are japan IP's and they never actually close,

1 solution is, TCPView, a small program, you can unzip to any folder and run without install, its free from Sysinternals,
you can view all TCP & UDP connections and close all the wait unclosed ones if desired, i use it myself and its helpful, dont close the established connections.
Download It Here