The server hosting the website, svn etc was changed today; everything's now running on the new server, but some things aren't fully configured yet, however the main things (site, svn, mail) seem to be up and running properly.

I'v been testing and tracking performance issues in ed2k plugin, due to several reports of Hydranode's ed2k plugin being slower than the other ed2k clients. Thankfully, we have extensive logging capabilities in ed2k module, so optimizing/fine-tuning the module simply means going through hundreds of megabytes of log data. We currently have two tools for this job - srcstat.pl, which does a overall analysis, and displays various statistics, such as average download-session lengths, percentages of failed/succeeded udp queries etc; and a newly-added commlog.pl, which splits the trace log into per-client log chunks, so you can quickly see all data for each client, separately. The output of the latter is what makes currently debugging it really easy, since I no longer have to grep the log by ip all the time, but I can simply scroll through the post-processed log and see how each client behaved, where communication ended etc, including the timestamps of each operation.

Based on all that data, I'v managed to discover, and solve a number of issues of various nature; the details of those issues aren't relevant (you can see them in the corresponding checkin messages); theoretically the performance is getting better, but outside confirmations are missing yet (should get some outside reports in a few days hopefully).

Madcat, ZzZz

PS: I'm looking for documentation on Azureus PeerExchange protocol (equivalent to ed2k sourceexchange), as well as Azureus DHT trackerless system - to my knowledge, no documentation on it exists; please prove me wrong.