[tor-dev] onionoo resource requirements
karsten at torproject.org
Mon Apr 27 17:39:53 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 25/04/15 22:33, l.m wrote:
> Actually I've been meaning to ask a question related to this. I've
> been wondering if, during the development of Onionoo, you
> considered any other frameworks? I'm not familiar with the history
> of Onionoo so I don't know if you made the choice based on some
> constraint. I read the design doc which made me curious.
Most design choices were made in favor of making the web front-end
part scale. It's a response to building some services like the
(discontinued) relay search that started with reasonable performance
and degraded a lot over time. It's why, in Onionoo, responses are
written to disk by the hourly updater and not put together on-the-fly.
And it's why all requests are handled by an in-memory index of all
documents rather than by a database. I'm not saying that no other
design can achieve the same performance, but I find that much harder,
in particular with respect to performance variance.
Not sure what frameworks you have in mind. But I'm happy to hear more
about frameworks that would make Onionoo easier to extend and not
perform worse (or even better) than now. If you have something in
mind, please say so.
All the best,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
-----END PGP SIGNATURE-----
More information about the tor-dev