[tor-dev] meek-server performance improvements?

[David Fifield]

I saw you say on IRC that you had an idea for improving the efficiency
of meek-server. What's your idea? The server hosting meek-azure is
passing 90% CPU at times.

One idea I've seen is using one connection for upstream data
(data-carrying POSTs, emptry responses), and one connection for
downstream data (GET, one big chunked download). As I understand it,
this is what Lantern's enproxy does:
https://github.com/getlantern/enproxy
So far I've avoided this idea because of the possibly weird traffic
patterns.

I've also done some preliminary work on allowing the server to send data
in larger chunks, which should reduce polling:
https://trac.torproject.org/projects/tor/ticket/12857#comment:4
All that's really needed here is a decision on how to let the client
indicate that it supports such a server, as the change is backward
incompatible.