Outline · [ Standard ] · Linear+ GUI freeze on connection - 2 CPUs

[Zom]

Well, in fact it's not good to share that much (>1000 files)

I accept the warning about >1000 files, but I was sharing 5200 files on the single CPU machine with no problems.

...  it's exactly 1000 + 1 the number of files in shared list that give you the problem? how much shared files do you have when problem start?

I cannot be exact about when the problem starts, but it is over 1500 files. I went up in multiples of 500 or so and 1500+ was OK but the problems started just above 2000. If the precise number is important I can spend more time working it out. It is easier when I can just add or subtract folder trees from my share.

btw, there's nothing related to hashing of big files in the log ...

I saw nothing related to problems with hashing. I have hashing priority set to standard. Locking still occurred on connects well after all shared files had been hashed.

It is difficult to make this machine work hard. eMule must be doing something *special* to use so much CPU.

[Vladimir (SV)]

Well, currently I testing to add ~26000

While testing I noticed some things:

1) Adding "program files" node (ctrl + click) to shared files takes almost 7min just to select all sub-folders! ePlus was freezed during that time and I lose all my active download/upload speed.

2) Even when hashing and processing the list with the 26000 files ePlus is able to reach top speed (download/upload) but system was unresponsive and ePlus is taking 99% of processor. This might be normal, but I don't know as I had never hashed 26K files before

3) I had to set emule.exe to idle priority to write this...

Well, in fact it's not good to share that much (>1000 files)

It is difficult to make this machine work hard. eMule must be doing something *special* to use so much CPU.

An empty-infinite loop can do this even in VB6... just put a Do/Loop with nothing inside and your pc is frozen.

[Zom]

An empty-infinite loop can do this even in VB6... just put a Do/Loop with nothing inside and your pc is frozen.

I would call a do loop doing nothing forever *special* It is one of the things bounds checking is for, yes?

Again - I had no significant problems with a single CPU PC and 5200+ files. Its only when I went to dual core that the problems started.

[Zom]

The problem is still there with 1.2a but it manifests slightly differently. The CPU usage is now choppier and more evenly shared between the CPUs.

[Zom]

This bug still exists in 1.2b

[muleteer]

Difficult for us to fix what we can't reproduce. You'll probably have to wait until one of the devs gets a Core2Duo.

I suppose you have the latest BIOS from the Intel website.

Are there options for turning off Core2 related stuff in the BIOS? Can you try testing various combinations of those and find out what is breaking eMule Plus?

Try a clean install of eMule (the original eMule). Does that have the same issues? If not, the devs could probably compare the code and figure it out.

[Aw3]

Do you have PartTraffic option enabled? If yes, what is behaviour without it?
There will be difference based on which window is selected. Shared Files window will probably show worse results in comparison with other. When you captured those screens, which page was active?

Is Lancast option enabled?

How does load increase? It happens suddenly or slowly growing while adding more files.
Could you please find the number of files after which you can see a peak load (just in case there is some relation)?

[Zom]

I suppose you have the latest BIOS from the Intel website.

Yes I do.

Are there options for turning off Core2 related stuff in the BIOS?

Yes there is a facility for disabling the secondary processor(s). It makes no difference when the second processor is disabled, except that the single processor is pinned at 100% instead of two processors running at about 70% each.

Try a clean install of eMule (the original eMule).

Can I do that without compromising the existing plus install?

Do you have PartTraffic option enabled?

Yes. It makes no difference when it is turned off. The servers page was active when the graphs were imaged. (It is not possible to move from the servers page because the GUI is frozen)

Is Lancast option enabled?

No.

How does load increase?

When the GUI freezes it snap freezes and then snaps OK again. I spent some time doing file number experiments, and the GUI freezing starts around the 2000 files mark. The interesting thing I noticed this time is that the length of time the GUI freezes depends on the number of files shared, but the relationship is not linear. For 2237 files it freezes for about 15 seconds. For 3000 files it freezes for about 30 seconds. For 5000 files if freezes for about 120 seconds.
The freezing always occurs during server connection.

This post has been edited by Zom: Feb 13 2007, 09:22

[muleteer]

Can I do that without compromising the existing plus install?

Sure. Just install to a different folder. Don't delete your old installation - you'll want to get back to it after you're done testing.

This is looking more and more like a threading issue. Scenario: To speed things up, the two processors split the threads between them, then they fight over them.

This post has been edited by muleteer: Feb 13 2007, 09:52

[Zom]

Try a clean install of eMule (the original eMule). Does that have the same issues?

With the original Emule, using the same ports, on the same PC sharing the same 5200+ files, server connects are almost instanteaneous with no GUI freeze or large processor usage.
Probably not good news for the plus team

[Aw3]

Try a clean install of eMule (the original eMule).

Can I do that without compromising the existing plus install?

Don't do that, it's not related.

I found the cause of the issue. Later I will give you a version to test.

[Zom]

I found the cause of the issue. Later I will give you a version to test.

Cool! - timeframe?

[Aw3]

Read your PM...

[Zom]

Outstanding! That fixed it completely. Not even a hiccup on server connect. No sign of high processor usage.

So now I'm curious. What was it?

[Aw3]

That was pretty bad work with the list resource which caused a lot of unrequired updates and other bad things. It's hard to notice it for the short list, but it grows exponentially for the long one...