Hi
In INHO DC++ is swallowing way to many resources. I have made a couple of tests on a couple of different machines amongst which where a Pentium 4 2.4, Athlon XP 2200.
In all test DC++ is using minimum about 20% of CPU and sometimes it rises to 70%. This is way to much! Even 20% is way to much!
I would recommend more effort on the resource part! As DC++ grows with features and advancement, this problem isn't going to decrease.
Best and kind regards
Resource swallowing improvement
Moderator: Moderators
-
- Forum Moderator
- Posts: 1420
- Joined: 2003-04-22 14:37
What was DC++ doing at the time? Without this information, you measurements are completely abitrary and meaningless.
Information on all of the below are needed:
* What version of DC++ are you using?
* Was DC++ hashing your share?
* Was it refereshing your share?
* How many hubs were you connected to?
* How many users were there in all those hubs?
* How many transfers were happening?
Information on all of the below are needed:
* What version of DC++ are you using?
* Was DC++ hashing your share?
* Was it refereshing your share?
* How many hubs were you connected to?
* How many users were there in all those hubs?
* How many transfers were happening?
Yes these questions are ofcourse important. I didn't mention the information because I just find that DC++ is very resource swallowing in general.
11.000
10.000
7900
7700
7300
4000
393
367
448
270
This is the average. This consumes about 20-70% CPU, it goes up and down unstabel. On average it is about 50% CPU and 93.564 KB of memory.
The newest stabel 0.698.* What version of DC++ are you using?
Nope. The test is startet after the hashing.* Was DC++ hashing your share?
Nope. Refresh is off.* Was it refereshing your share?
10 Hubs on a 10Mbit line. The same hubs are used.* How many hubs were you connected to?
Aprox..* How many users were there in all those hubs?
11.000
10.000
7900
7700
7300
4000
393
367
448
270
Starting 10 - 12 transfers, transfering big files. Speed lies at about 400 Kbit in total.* How many transfers were happening?
This is the average. This consumes about 20-70% CPU, it goes up and down unstabel. On average it is about 50% CPU and 93.564 KB of memory.
DC++ gets laggy while being in hubs with more than a couple of thousand users. Which is fine by me since they're all crap anyway Stay in smaller hubs and DC++ works well.
"Every Englishman must have a hobby. Some like to collect the stamp, some like to make the jam, but the most fun is to a kill a little animal with a shotgun or rip them up with wild dog."
-
- Forum Moderator
- Posts: 1420
- Joined: 2003-04-22 14:37
This does effect the CPU usage a little bit, but not much.Hide the user lists in the hubs and see if that makes a difference to the CPU usage.
My opinion is that DC++ in general is too resource demanding. I have made this remark so perhaps in the furture a more effective way of dealing with resource will be taken into programming considerations.
DC++ is getting more and more heavy on each upgrade and eventhough features are really cool, an effective way to have DC++ running in the back without eating to many resources is a goal to keep in mind.