At the moment the priority is the CPU/memory performance issues which have been reported fairly widely. A big part of this comes down to object churn, and I have made significant progress on this on Saturday. But I seem to have broken something fairly major in the process. I will therefore fix this, and do some more work on this. Testers would be helpful; I know there are issues with the build I committed on Saturday (1ms ping time, backoff, ...), but even there I'd like to know more about how it fails.
Once this is sorted I will put out a new build to the auto-update (there are reports of this not working, but I think that's just due to 1010 USK breakage). bback seems to have taken on the FCP changes that need to be done, so that leaves me free to get on with the remaining major issues: - Aftermath of 1010: Auto-update keys, ARK keys etc will need to be changed; if I have any peers still on 1009, I need to start up a node and insert the auto-update to them (although the network may be too fragmented for this to be of any use, it's worth trying). - Backoff / load limiting. Once the current issues have been sorted hopefully this will improve. - Location clustering / routing issues. May very well be caused by lack of opennet, but further investigation is required. - Opennet. PS Some people have complained about my absence during most of January. A big chunk of this was (unpaid) sick-leave; the rest was (also unpaid) holiday time. I'm back now! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070205/65396cbd/attachment.pgp>
