aMule Forum
English => en_Bugs => Topic started by: woutermense on September 21, 2010, 08:04:49 PM
-
The aMuleD has been running for a while now and the logfile has become somewhat big. It's a 250kB file with 3000+ lines of log in it. The daemon is running remote and is accessed via Gbit LAN. After starting the GUI, about 40 seconds is required to transfer the entire log. Fortunately the log is downloaded last so I can still see the state of my downloads, but I have to wait for it to finish transferring to actually be able to do something, like a search for instance.
-
The slow transfer is actually a feature - aMule is transferring only a certain number of lines per communication cycle.
EC speed is not controlled unlike download speed, so it tries not to clog the connection.
Actions should not be blocked however. Please open a bug in the tracker.
-
Well I'm not sure it blocks the actions, but say I start a search at 20 seconds then something will start to happen (search result shown) only at 40 seconds after starting the gui, when the log transfer is finished.
bug filed (http://bugs.amule.org/view.php?id=1627)
-
So the SVN version shows amuled's log? Good to know. But who needs _all_ the log file from the times of creation? If I have long uptime (several months), then my average working time in amuleGUI would be less then the time needed for transfer. May be several last lines would be enough? And the rest - on request, for true masochists.
-
You can always clear the log every now and then.
-
Yeah there's a HUGE reset button next to the logs.
If only it worked ;)
-
Sigh...
Be so kind and file another one. Can't say when I get around to fix that.
-
Button implemented in 10294. :)
-
Well I'm not sure it blocks the actions, but say I start a search at 20 seconds then something will start to happen (search result shown) only at 40 seconds after starting the gui, when the log transfer is finished.
Can't reproduce that.
I logged 10000 numbered log messages in amule and then started amulegui.
After it was up, I started a search, and got results at normal speed.
Switched to logs tab, and it was still at log line 1500.
-
Button implemented in 10294. :)
Gonna check out that code :) I wanted to try and code something myself but failed at finding out how there was any log displayed in the first place.
Well I'm not sure it blocks the actions, but say I start a search at 20 seconds then something will start to happen (search result shown) only at 40 seconds after starting the gui, when the log transfer is finished.
Can't reproduce that.
I logged 10000 numbered log messages in amule and then started amulegui.
After it was up, I started a search, and got results at normal speed.
Switched to logs tab, and it was still at log line 1500.
Bummer... I can't either anymore. I try to be careful and post reproducible bugs only. Maybe the server (running amuled) was busy or something. If I run into it again I'll follow up.