onionoo: grouping families in the backend?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I figured it might make sense to discuss this in a separate thread.
And just in case you were wondering, if you ever have a feature request for Onionoo, I'd be happy to discuss that. In contrast to some of its clients, Onionoo itself is actively maintained.
Actually I came to the conclusion that it would make sense to move the myfamily grouping to the backend since any other compass grouping is based on onionoo data and not on data "generated" by compass itself (grouping key). The MyFamily grouping takes also a bit CPU time. So "computing" families once per generated details document make a lot more sense than recalculating them in every compass query again. Since the MyFamily is subject to change [1] is also relevant here. [1] https://lists.torproject.org/pipermail/tor-dev/2015-March/008516.html -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVEBuLAAoJEFv7XvVCELh05MMP/0Gy6zYQLbZtavXL1wdISLMg X/zdJM9+ZysuFkDj2hl0fP1iXfrNCCCvjCOdCYQJXzD5axrvgzPK/Jql1b2J1tO5 m+fbkLla9/KRCukJKYOjmkeoKAuadRDiZvI9LvePuGPrP53ZmlJmh4PT/Iss8Qh+ ndTBIbz1Kl04cBVS8RW08veFIKyzblkd2bJVj6AIlsvRvNybLJdEatgNAJ0YX6Vk ERuWuI65qP40ATFMAmL+IMsrdJ2WVdhpbbFLNkrZfloXt/UlNvFddMKlJ0k3YUkb ZQsFmZUPPv9+gMGx7Rkca94XmleBxMidjAbDVT0Y+SVyC0HxEOa5UsZ099cVu52F Hf2ZHt2E6vSxICoO4lxFEx82BxuaJLvG/+pQcNmUQk+SeBlcYn/W6PIyYV1bs9sh /pLjikLnMEMpNCls5XNc/wtFJtbnfljmsDhYL+R5jCHfUk5s3XmyEuDitenwZ8Qb 3u4qtnusQqLzW0R2bcnA8OV5RU5N12kBmFnki2lZ+m7VKtHCQVgJP8Rpvfg7G0/6 Js36UnNL2ijMNuDJED70PZEPop8kiuSZq6ePI3lYsPaLLRGLmNyHCgFQFRBox4BK ntAiePf2HtQ1kSLM2j5GLrQK5p59ko9xXrQkRBy60M5oVJkl+Rtf/+79W0Nf9f8Y /rcCkyU4s7XqW0UoHMYQ =ly6d -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 another good reason to move it to the backend: Virgil (also using MyFamily data to group relays) and any other application using onionoo can also take advantage of that (no need to re-implement it n times). -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVEBzYAAoJEFv7XvVCELh0VcUQALl6VpJkHJH0DSMg7sMfKJ1s ys8d1Kf2xQJm3ygXyYSth0/IB6dF6g5Jc6GEUYaWolNYMPygzncb1s1cVIh470QP SvdBBXEjghmESfyVIUBbINmqHAVwdIzjWPne9azJJm0uc0twF0yx+Lz6WOlBmcH/ OQcOUo2YBz1UMy8rPNdrmEsjMriKGiwfp1F7SXbBj+P08/m2uc3b1Jo7sbCejesX bOKxts0l9wBkiWSu072bLijRVx3Upn13bhYZ8Z/F+XRHRc0+AzCgCwUJcMfFcZmn WrNrIZrcgjIfynb/qM9GkaP39cC1QLnoSJ8NVS1NHQ9GGQNRUGgWsY3WwIGoJYsK g6KsYXydhxDw/shloV/hqHdyLKsBFr9qKymasXQ/BSD2dtyzkv0JncPvICDBcOBx F4nMlYKrAXeS9LPbY/okSQrDygimffFlwmhi8IKc9hW2ZmRyKWzeKVt9/gYvSTgS RF33ZfXGLI8jVlk834xVuv35JmRjhFDXpzhlYXPVKVsqWGJDr8tbRBX2oiZ1Y34L E5OWPs+7l7FKjp4tBpEx3wdJAY6vRd6U0bl/AatpbrXDvGxUgk8BXz5cAPP7gxLV HcdhNac2sfSh7PjMVFPy9GFIU+h9rq+uS1fln7Qp4xWGm6FThaAn/XzZvpwyGWTK E64z79N7+odYxeRrxMWf =CaxB -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Nusenu:
I figured it might make sense to discuss this in a separate thread.
And just in case you were wondering, if you ever have a feature request for Onionoo, I'd be happy to discuss that. In contrast to some of its clients, Onionoo itself is actively maintained.
Actually I came to the conclusion that it would make sense to move the myfamily grouping to the backend since any other compass grouping is based on onionoo data and not on data "generated" by compass itself (grouping key).
The MyFamily grouping takes also a bit CPU time. So "computing" families once per generated details document make a lot more sense than recalculating them in every compass query again.
Actually it is be a lot easier then I tough and does not require a backend change at all, so you can ignore this one. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVECKjAAoJEFv7XvVCELh09csP/1WURzPDEZQ23zo3BzA9K8PY 3ubeSLeh2wecp/l0DNvA+vg4PwslDfFnTLeesyjtGR6Z9M0ab6GoyJvDZPiJ/pUm 8HzOpE81KfdeqCkzBrk4nv0z+KOV3ITrjjr6k5uX3DJ0TVj0DdxtrPSHAh3F5li5 CBPA2XayIuyW3Pg5lQXLQPm+TILjv2PkEfhDElfnvGwp4kH8/desMwYEJ1xVSpiD Un7wSHP0DKxbh17OkxlEBwGqN+5a5EcGrcL/RLRLdDeeyqjIFeQ6kvEReseH+3dN M/9yxVs9yA5Q9HJSO8tg9J47TwUoX43uds6i6pzfezB+gr+HbZviWmJh5PI2V66d fYw/d4Qi4IgwdNseuVzr2Z99+XEWfk/ZrkhmdB50wKxyrUM/9UlKbgqcHmUDifcR SWyF4emygElZjD2zhpQ28HiaCN6Nfq0Kd2bNfuSRn7ek/S5n2JOHjIvpju5Bni+C GVh4Of7NrwoFVK3dexO9C3IwT1D39NDY+NZsK4GSAhw0JGB30eYzKLABaQWUUB0C Ukp8kV6MqmgYqjx88l2VQN7VkrTkhFc/O/QoA/bZefskiOV0utruYCGUM1SbUSQw u0eJUdRAg68UP2ni2jgqw5ND1bj/ZJR5jTdPQN6DaScqNwaG6AZy1ClKTITHuqWn 6J2pWvgsGGfzjTf7mO39 =chND -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/03/15 15:26, Nusenu wrote:
Nusenu:
I figured it might make sense to discuss this in a separate thread.
And just in case you were wondering, if you ever have a feature request for Onionoo, I'd be happy to discuss that. In contrast to some of its clients, Onionoo itself is actively maintained.
Actually I came to the conclusion that it would make sense to move the myfamily grouping to the backend since any other compass grouping is based on onionoo data and not on data "generated" by compass itself (grouping key).
The MyFamily grouping takes also a bit CPU time. So "computing" families once per generated details document make a lot more sense than recalculating them in every compass query again.
Actually it is be a lot easier then I tough and does not require a backend change at all, so you can ignore this one.
Okay, just in case you change your mind, let's talk more about integrating this into Onionoo. There's already the `family` parameter which I specifically added for Virgil's thing. Though for Compass (or its successor), you'd probably want a new field in details documents, not a parameter. Just let me know. All the best, Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJVECt4AAoJEJD5dJfVqbCrKAUH+gK9pOThFkS70gidRV5PpmFJ ZmtlQzVBrq9iGdB/IxczKbTer5a3P81Moy8Y6S9K6fwAMasWVyfxOOq078iVnjly n1rhc1kaDRqlyo8oSAlzZDC5mW2MhOcloFJsMUOLryWkjPDGTUC8VpTMhKv1YWWs BPlhTeNBQjbtWYZbGbkVeCSbheT0amSJokfvOdAcxoIX++9WZRLG9L1IhDodo89i v8IU952Q7x7Qg8Cs67f7wQy1MjIqXavmu2zxMffUPVtaqXunG8zkDYdJYzNVfrOl O5gjv/oi96dawh8/f4FXJL9n0gRzNl5clV1LVTo2aUV9nAVvqTyuNuOfOQgmug0= =IlKR -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Karsten Loesing:
Okay, just in case you change your mind, let's talk more about integrating this into Onionoo. There's already the `family` parameter which I specifically added for Virgil's thing.
Yes I'm using the 'family' list as well now - perfectly fits my needs. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVEC63AAoJEFv7XvVCELh0NfMP/0qLIfBOx3d4IT82+3a1N4m0 PXmBQwOTCJI6lMj7R3yOpBrFz9JAbzWmiP8UquJ0vG5a2DffGL29SoUr3dvOIsnR NLcjOfuPN5ezy41t4C1bzAYUjR9lJNHKx9ZJab35moqkwd5gFSX5JmnD/+jm9ZZ5 /GtAXAFD5/YIXv+hNeFqqdH4zTpju8T7EWwAiSiqbfYP8JUBE+Bhr0smE6xtNWCp yPSo+MbGd/U9KLUKSU7XlTBYxBip0F47JBW1yQ0EEjbxt2D7JndyaTWOiGSaOT5v Z379XBHs+XI178GOkt06j8VqeUjjcaNr51o0H51/R1gVoQQdHdCihDCgg0Rg7+Rw ZKHV6tnHk4dtQiACH2rdpxnBm8Hoew8kOfVma0WgzoZGCWM0GKKR6uximxYxsNV5 ViIbSv41UsJpD/qA9drZbBRkc97pO+GO6dTGSKuBSDlLwZeKHPi9cFzu2nyx9ym3 i7fVr9UGRNIWX/3S4798vmRmqLdOQ3VoRWo+nMvzuSs0C3TS1j8HZQC3T5uljo/y Md0O3G6BQYgbS/xvcnaA/PdotftJDt3aG2G/rjWlit3ko4IWFFMVXx4i1S1ighzN iy4TUlEcRwcyy4me00BJbpyqVDNLhljYXO6Qxqs36aAcqyl0E2PNf3EKgEwsmUxM RafKD5DotGVl/wR8cylo =GKel -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Nusenu:
Okay, just in case you change your mind, let's talk more about integrating this into Onionoo. There's already the `family` parameter which I specifically added for Virgil's thing.
Yes I'm using the 'family' list as well now - perfectly fits my needs.
After comparing results of different group by family approaches (expensive vs. simple and fast) I noticed the simple version does not come without a drawback (requiring perfect matches has its consequences), but I'll play around a bit more before coming to a final conclusion or before requesting any backend feature. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVEHlIAAoJEFv7XvVCELh0tAgP/A4XxnYBAadqfVZheGC9l/N1 8SAAncjjbH6obDMMfCueOCHQwbb5oWWUXN7LSzf66zsmQHxbzauy/giwgWiODIR1 OPMvbPUtQS3tz7Ur6wGuhd+53isUUaR3BlcYSXnyfz9NyMuzlMUd4NZ46Mal6Xcd GkgcKjeyP+WxzG8nFzD1LPm3cb2kQox4RnJlOtsqV1BI3oWy3Xk+ls41JXH2t93e Gem0ZdJ2uXN2p9ay7V+mhcxPS+Eobl/TIoI8RuNyNzNgZO95tusdk4CNbqsk1gFX zI5Y25DiB788LIsWD8eLc1K+BRgeWbow3n7CD7N5+WR3TjMwpoHiZQJIM1rJOEOY AXIUPK9h8/iaBVvTrStZcxs2IrjpxE7R4a3C1Ry/Jll1/5cN2BWPDE/4ObTQyQme AfHDp0qGJK85Lc9w9VLOi4tEUC32FHzvgmNdju2sIbkJUF4fPCFe09nZUtJ4OHjV qbodUZryoQdh7MxOyfv3I391ns6ML2POohcP7+JXhR1CDloowyA8FNrjVe21JkYN lQPhg8i6bWGJqp+jQK9z2KA7jjv8I0IMO2AHNdVoRx0yJ1/xJARAMqWeqBQW8Qaw qPsPwfGqORWkRrHVf16/a4EYlnqni5OYWobPVCulyLxJty+gVZGX+TYLIhANuAfF joHGjhZG8Cs7JQROb+c7 =rPiV -----END PGP SIGNATURE-----
participants (2)
-
Karsten Loesing -
Nusenu