[freenet-dev] GSoC 2012: Network Probes, Statistics, and Analysis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I was hoping to get some feedback on my Google Summer of Code application. I've noticed that the lack of detailed information available on network topology, link distribution, and overall makeup and health makes it difficult to make decisions on how to improve network performance. To that end, I'd like to: - -Clean up the existing probe code: document, improve readability, and correct errors and annoyances. To name some examples: -Peer locations are reported as doubles with known/unknown, backed off/not backed off encoded into the value, and there are some ambiguities in these values. I'd like to make a Location class instead with separate reported fields. -Probe traces can still be returned after a completion message; waiting a while for more traces could be nice. - -Make probes available over FCP: -Document along with other FCP messages. [0] -I've already started initial implementations of these changes in Fred [1] and lib-pyFreenet. [2] - -Plot network attributes revealed through probe requests: -Node churn -Network size -Link length distribution -Graphs of topology: Gephi [3] could be useful here. -I've already started an initial implementation of such a tool. [4] - -Implement the probes and traces described in bugs #3568 [5] and #3550 [6]. I don't have experience adding new message types to Fred - I've only registered a message type from a plugin [7], so I'm not sure what it involves or if it's within the scope of a summer. I'd appreciate anyone's thoughts on this. Is anyone willing to mentor me on this project? Thanks, Steve Dougherty [0] http://new-wiki.freenetproject.org/FCPv2#Messages [1] https://github.com/Thynix/fred-staging/tree/FCPProbes [2] https://github.com/Thynix/lib-pyFreenet-staging/tree/FCPProbe [3] http://gephi.org [4] https://github.com/Thynix/pyProbe [5] https://bugs.freenetproject.org/view.php?id=3568 [6] https://bugs.freenetproject.org/view.php?id=3550 [7] https://github.com/thynix/n2nchat -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPc+bUAAoJECLJP19KqmFufdgP/3nq2E4YPHNYDUQNTxupZdl9 9p2lpk7379z1nvdUzNsebiSqA6bIL0vE8hgJ/7bnw37qHkjbbshOvejChoaF0jqY aYEZmVYqbqP4RPrxGV+hxndGSBDadn4iCdoMeABFsGfa1BqFEgLaOAkuXT0zFF5D SWGZZzCRx7h+JIA2Iv5/oKgoeSgb+Be6UaoJv3niheh9iZv6Qo3LQU9ZfQNG/Dx1 SZEdl0NePNQUGLEztpFZGs9wwdXSPisVIVckRtELB5B5zc5m4qb26u9zGDqBiVCs JCnf9GfYDlX6BH90bCT1qujroIh1l/Frx06akbMQw8YLOCxkO5mJlnehxxELf5le cdh+z2lsLKyouRROtHVcIMhhkAjTiu2cZhHvM5KmbfRVbPDwsqdIuEQPO87AGwoa uIS/3So/s8EycA0nwv+TErfQfEcRguTVvE5w5L9hN6vmznt2J0LeKy55ZzpJItTU EHudI4qXDxr4SwOJAPH2rfOUWF4935rLchHlI/IGQagqDqPnWznsTaKNmdz1XBdF UftRo75Z1qgoINyLTFpZ2H2LFJ2wnvPHnbhLynQslbskjZzeVnRTP/6Td0sE94Dw qqMvPWbNzbEkX6FObSM7ogXaPOKfkpjm5xW4zuj2GR8F5xR343HyPAQ1xZPkJ7bp WNeVIlfmO1OKHNMBbnlx =VcWw -END PGP SIGNATURE-
[freenet-dev] GSoC 2012: Network Probes, Statistics, and Analysis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I was hoping to get some feedback on my Google Summer of Code application. I've noticed that the lack of detailed information available on network topology, link distribution, and overall makeup and health makes it difficult to make decisions on how to improve network performance. To that end, I'd like to: - -Clean up the existing probe code: document, improve readability, and correct errors and annoyances. To name some examples: -Peer locations are reported as doubles with known/unknown, backed off/not backed off encoded into the value, and there are some ambiguities in these values. I'd like to make a Location class instead with separate reported fields. -Probe traces can still be returned after a completion message; waiting a while for more traces could be nice. - -Make probes available over FCP: -Document along with other FCP messages. [0] -I've already started initial implementations of these changes in Fred [1] and lib-pyFreenet. [2] - -Plot network attributes revealed through probe requests: -Node churn -Network size -Link length distribution -Graphs of topology: Gephi [3] could be useful here. -I've already started an initial implementation of such a tool. [4] - -Implement the probes and traces described in bugs #3568 [5] and #3550 [6]. I don't have experience adding new message types to Fred - I've only registered a message type from a plugin [7], so I'm not sure what it involves or if it's within the scope of a summer. I'd appreciate anyone's thoughts on this. Is anyone willing to mentor me on this project? Thanks, Steve Dougherty [0] http://new-wiki.freenetproject.org/FCPv2#Messages [1] https://github.com/Thynix/fred-staging/tree/FCPProbes [2] https://github.com/Thynix/lib-pyFreenet-staging/tree/FCPProbe [3] http://gephi.org [4] https://github.com/Thynix/pyProbe [5] https://bugs.freenetproject.org/view.php?id=3568 [6] https://bugs.freenetproject.org/view.php?id=3550 [7] https://github.com/thynix/n2nchat -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPc+bUAAoJECLJP19KqmFufdgP/3nq2E4YPHNYDUQNTxupZdl9 9p2lpk7379z1nvdUzNsebiSqA6bIL0vE8hgJ/7bnw37qHkjbbshOvejChoaF0jqY aYEZmVYqbqP4RPrxGV+hxndGSBDadn4iCdoMeABFsGfa1BqFEgLaOAkuXT0zFF5D SWGZZzCRx7h+JIA2Iv5/oKgoeSgb+Be6UaoJv3niheh9iZv6Qo3LQU9ZfQNG/Dx1 SZEdl0NePNQUGLEztpFZGs9wwdXSPisVIVckRtELB5B5zc5m4qb26u9zGDqBiVCs JCnf9GfYDlX6BH90bCT1qujroIh1l/Frx06akbMQw8YLOCxkO5mJlnehxxELf5le cdh+z2lsLKyouRROtHVcIMhhkAjTiu2cZhHvM5KmbfRVbPDwsqdIuEQPO87AGwoa uIS/3So/s8EycA0nwv+TErfQfEcRguTVvE5w5L9hN6vmznt2J0LeKy55ZzpJItTU EHudI4qXDxr4SwOJAPH2rfOUWF4935rLchHlI/IGQagqDqPnWznsTaKNmdz1XBdF UftRo75Z1qgoINyLTFpZ2H2LFJ2wnvPHnbhLynQslbskjZzeVnRTP/6Td0sE94Dw qqMvPWbNzbEkX6FObSM7ogXaPOKfkpjm5xW4zuj2GR8F5xR343HyPAQ1xZPkJ7bp WNeVIlfmO1OKHNMBbnlx =VcWw -END PGP SIGNATURE- ___ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl