seastar

It's great to see people still using C to make web servers ! But can you clarify what are the "state-of-the-art technologies and solutions?" I just skim the project and think this is not a lot better in term of performance than other servers like Nginx or H2O. There is also Lwan[0], which uses epoll too and has a cool coroutine, router implementation (I implemented a framework for Kotlin/Native on top of it[1]). Another framework having really fast and fancy technologies in it is Seastar[2]. I think implementing kernel bypass, AIO, DPSK stuff makes it the fastest web server around currently. May be you can try to push the boundary with those things, SPDK, aggressive polling, fast router...? [0]: https://github.com/lpereira/lwan [1]: https://github.com/KwangIO/kwang [2]: https://github.com/scylladb/seastar

I haven't read the code, but there are 2 areas where I expect allocations: - The continuation which is passed to .then, and which is typically a closure, must be type-erased, which requires an allocation. Storing the continuation in a std::function would allocate too. A short glance at https://github.com/scylladb/seastar/blob/master/core/future.... also confirms that there is a make_unique there. - Since continuations are most likely not called inline on completion but deferred into the next eventloop iteration there needs to be a dynamically sized queue to hold the ready continuations. I am not 100% sure if that's the case for seastar too, but I would guess so.

Seastar/scylladb is looking for custom filesystem for per-core dbms https://github.com/scylladb/seastar/wiki/Google-Summer-of-Co...