3 ms·
It looks cool. The DB library is appreciated. However, you would get about the same idle memory and docker size with Go's Fibers framework :)
by winrid 4y ago
It looks cool. The DB library is appreciated. However, you would get about the same idle memory and docker size with Go's Fibers framework :)
- williamcotton 4y agoLol, yeah, the libdispatch runtime is probably about as big as the Go runtime! I think this has a slight advantage in that it uses a memory arena for a per-request bump allocator so it should keep overall memory usage lower. The slowest part of all this has to do with Block_copy and the places where I’m very much treating blocks/closures in an OOP type manner. This could be fixed by writing a different function that did basically the same thing as Block_copy but for all the “methods” on an “object” in a single pass. But who has time for that? :D Here’s more about those performance issues and some example code that show how slow the approach is: https://github.com/williamcotton/express-c/tree/master/research/blocks https://github.com/williamcotton/express-c/tree/master/resea...
- preseinger 4y agogo-fiber is a weird, non-idiomatic, and non-serious project, fine for a proof of concept, but definitely not something anyone should be using in prod but your point is sound, any reasonable go http server will have the same level of memory usage at idle
- winrid 4y agoWow, really? The project has 25k github stars and 300 contributors. They are on v2.44. Why is it not serious? What makes any software "serious" to you?