There's part of your problem. Running anything under Wine, not just eMule, on a 400 MHz Pentium 2 is going to eat up significant CPU resources. If the wineserver process can typically use 5-10% of my 2.2 GHz Athlon, then your 40% is quite expected don't you think? That's not to say that Wine's runtime couldn't be better optimized however.
Well, first of all, any sane GUI software should not use any CPU when idle. It has to be in "waiting for events/signals/interrupts" state, i.e. all threads would be sleeping waiting for events such as network packets arriving or GUI interaction like mouseclicks. There is no reason for an infinite loop to take 40% CPU time.
OK, I don't know how wine is programmed. Maybe it has some loop which runs every 1/10 second.
But this still does not explain why the Webinterface does not serve the request in a finite
time, I have waited for like one minute and the page does not load completely. If it was a CPU-usage problem then it should at least finish after a certain time.
Besides this problem also occurs when I test it on my P4 2.8GHz main box in VMware ...
Sorry, I don't see what you mean here. Are you running eMule under Wine under Linux on VMWare?
Yes. My main box is a windows machine, there I run VMWare and in VMWare I ran linux to test eMule on wine.
So even with the 2.8 GHz backend wineserver/eMule use CPU like crazy and the Webinterface does not load.
This post has been edited by hszFS: 18 December 2006 - 06:01 PM