shadowlmd

I just tested it with 1.3.1 and it's still there. I also noticed that when limits are enabled, each source is limited to 512 KiB/s. So, if I have 3 active sources, overall speed is 1,5 MiB/s.

That's really weird. I've just tested it again on two files which had multiple sources, and both times it worked exactly as I described. I attached 4 screenshots to show what happens.

Not sure what you mean, but if you believe that overhead is the problem, you are probably wrong. Overhead can be like 10% of total speed, so, if I limit to 6500 KiB/s, either actual bandwidth will be 7150 KiB/s, or actual transfer speed will be 5850 KiB/s, depending on realization. But when transfer speed drops to 512 KiB/s, thats 100% not an overhead problem.

Ok, with 1.3.0 it is not as bad as before. Whenever I enable limits, my download speed is at around 512 KiB/s while upload/download limit is 6500 KiB/s (6,35 MiB/s). As soon as I disable limiting, download speed goes to around 7 MiB/s instantly.

Ok, thanks for reply. Will wait for it. :)

I have pretty similar issue with limiter. Whenever limits are enabled, my downloads instantly stopping until I disable limiting completely. I have set my upload and download limits to 6500 KiB/s which is a lot higher that mimimum requirement. Any ideas why can this happen? I'm running ApexDC++ 1.2.2 under Windows Server 2003 SP2. Most weird thing is that download starts at good speed for a second or two and then just freezes. Attached is a screenshot which displays everything.

Why rehashing everything? Do you even understand what is this topic about? The problem is that ApexDC++ does not add NEWLY hashed files to file list. Just put something to a shared directory and wait until it will be hashed, then check your own list.

Believe me, it will NOT work. When support "sez" nonsense, I will not try it. As simple as that. And before suggesting something like that without even logically thinking how could it really help, try to reproduce bug on your system.

I'm already happy with StrongDC++ which does not have this issue. And the option you are talking about is related to downloaded files only and only if download folder is shared. I don't share download folder and issue is not with downloaded files. Also, as it was said before, new files are actually found and hashed, but don't go in file list until /refresh typed manualy. This is definetely a bug.

This option is abolutely not related to the issue.

By the way, there is no such issue with StrongDC++ 2.11. I will stick to using it.

Yep, it has nothing to do with hashing, files get hashed after first auto refresh. They just don't get into share after hashing is finished and until /refresh manually typed.

Ok. In my case I added directories with subdirectories into a shared directory. Maybe this was the case. I didn't try to add just files to share. And I don't think it is coincidence, since not only I experiencing this issue.

I did not change standard refresh interval, and file list was not refreshed within more than 3 hours, though there were a lot of messages stating that file list refresh finished. It only updated after I manually typed /refresh more than 3 hours after adding files to shared directory.

Does not actually happen to me. I see a lot of messages in the log saying that file list refresh finished, but still if I open own list, I see old stuff there. New staff appears only if I manually type /refresh. Version 1.0.0B5.