Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GuybrushThreepwood]

First of all, excuse me for my long long absence. I haven't absolutely lost my interest in this subject but I've had some severe family problems and I couldn't make more testing anymore.
By the way, some days ago I've managed to download the latest 10306 (at that time, I hadn't still read the last post from Stu) and I've built it: though, according to the changelog, some fixes to the GUI have been applied in 10305, I've still found the same issues found with 10210. I can't see the statistics anymore under the GUI and, what's worse,  aMule is clearly struggling though the swap issue is finally over thanks to the signal handler disabling suggested by Stu.  
Now I'm going to download and build the 10140 like suggested by Stu (thank you very much as always! ) but before I'd like to know if in 10306 the GUI issues are still present or they're solved as it seems according to the changelog. Thanks for everything!

[Stu Redman]

Welcome back! Sorry to hear about your problems. Real life should always have priority over projects like this.
You must excuse however that my thinking process about your problem is more or less reset to zero meanwhile. 

There's nothing improving your situation since 10302.
I don't know when exactly the stat tree was broken but I'm planning to fix it before 2.3. There are more pressing issues atm though.

10140 will be worth a try, but I doubt it's better performance-wise than 10302+ . Versions between are a bit CPU load heavy on the core when the GUI is connected.
What exactly do you mean with "struggling" ? Can you compare performance with connected gui and without?

[GuybrushThreepwood]

Hi and thanks for your kind reply! As already told in one of my previous messages (that I perfectly know you couldn't remember considering all the issues that you have to deal with), with 'struggling' I mean that aMule shows erratic download and upload speeds going up and down and the hard drive connected to the router doesn't stop for a second and this usually means that it's swapping a lot. I hope that things are clearer now. By the way, in the meantime I've built 10140 as you've suggested and it's proving to be quite stable though I plan to test it more thorougly before saying a final word. I will keep you updated. Thanks for everything!

[GuybrushThreepwood]

Hello again! I'm continuing to test 10140 and it's still going well. I have two doubts though: you've said to me that 10140 includes the old GUI but I've tried aMuleGUI 10210 with amuled 10140 and it works, how is this possible if 10210 uses a new GUI? Something might have changed for sure because by now 10140 is much better than 10210 but I don't understand how could 10210 GUI work with 10140 daemon if these two versions use different GUIs...
Apart from this, even with 10140 I can't see the statistics: what's changed and what's preventing me from doing it? I'm not talking about the graphs (they never worked for me, probably because of some missing dependencies that I never cared about because I don't need the graphs and I fear that they're quite heavy to handle) but about the simple text statistics (average upload and download speeds, time connected, number of reconnections etc.) that have always worked like a charm for me with the 9xxx SVNs... Thanks!

[Stu Redman]

Well, it could work together somehow, but you're on your own with any problems.  
As I already said - stats have been broken for some time, and will stay that until I fix them.  Graphs have never worked and won't any time soon.

[GuybrushThreepwood]

Well, it could work together somehow, but you're on your own with any problems.  

Clear! I always use the GUI with the same daemon version anyway as I'm sure that's the best practice. That was only a fast check that I've done. By the way I can confirm that by now it seems that with 10140 the old good days of 9548 have come back (with a lot of new improvements too)!

As I already said - stats have been broken for some time, and will stay that until I fix them.  Graphs have never worked and won't any time soon.

Excuse me, I've missed that. For what concerns graphs I don't care about them at all. I will continue to test 10140 and when I would be sure that everything is fine I would write a post here summarizing the various modifications needed to make it work on my router (thank you for almost all of them! )
Just a last question: what are the changes made to the GUI afterwards that could cause my problems? Wouldn't I never be able to use any version newer than 10140? Thanks for everything!

[Stu Redman]

For the new gui the clients have to be transported through EC. Functions like showing uploads can't be implemented reasonably otherwise anymore. There is a benefit - double-clicking a download in amulegui didn't show the sources before. Now it does. (Single click to be precise.)
Collecting this info takes a bit time however. If your router is already close to the edge this might tip it over.

You can try if the clients are the problem by patching ExternalConn.cpp lines 663 +:

Code: [Select]

}
//// Add clients
//CECEmptyTag clients(EC_TAG_CLIENT);
//const CClientList::IDMap& clientList = theApp->clientlist->GetClientList();
//for (CClientList::IDMap::const_iterator it = clientList.begin(); it != clientList.end(); it++) {
// const CUpDownClient* cur_client = it->second;
// CValueMap &valuemap = tagmap.GetValueMap(cur_client->ECID());
// clients.AddTag(CEC_UpDownClient_Tag(cur_client, EC_DETAIL_INC_UPDATE, &valuemap));
//}
//response->AddTag(clients);

return response;
}
Please tell me if that makes current SVN usable for you.

[GuybrushThreepwood]

I will within a day or two and I will post here the results...

[GuybrushThreepwood]

Please tell me if that makes current SVN usable for you.

Hi! Unfortunately, I've built 10312 commenting those lines but nothing: it isn't stable like 10140 and the older 9xxx SVNs are, it behaves instead as 10306 with ExternalConn.cpp untouched... Are there any other relevant changes between let's say 10140 and 10210  that may cause my problems?
Just to keep things clear, 10210  was the first one of the '10xxx family' that I've built and it has issues too though somewhat different from the ones shown by 10306, please read these posts:

http://forum.amule.org/index.php?topic=17343.msg98190#msg98190

http://forum.amule.org/index.php?topic=17343.msg99495#msg99495

for reference. Thanks again!

[Stu Redman]

Hmm, please try 10191 (or little earlier) - before EC implementation of new gui, and if it fails too, 10145 (or little later) - right after intro of new gui.

[btkaos]

Interesting Guybrush. You could use "git bisect" in order to find the exact revision causing problems.

[Stu Redman]

Nah, do what I said. There are some versions in that range that you better not try. 

[btkaos]

I agree with you STU, but keep in mind that git bisect has log(n) complexity on the number of svn revisions.

Regards,
BTK

[btkaos]

In order to save you some math, the log(n) things means that if you need to try more than 5 revisions, you should use git bisect.

Regards,
BTK

[GuybrushThreepwood]

First of all thanks to you both for your replies. I'd like to use the git bisect function if necessary but I haven't never used so I would have to find out how.
By the way, I've chosen 10190 and 10148 following Stu's advices. I've left ExternalConn.cpp untouched on the both of them.
I haven't still tested 10148 but I've been using 10190 for some days now (I did't come back here before for that reason: I wanted to test it more thoroughly before saying a final word) and it proved to be quite stable. I have the impression that it's quite heavier on resorces than 10140 but it seems to work well. Now we have to understand what are the changes made between 10190 and 10210 that could cause my problems... I'm free to help should anyone of you need some more detailed informations.