On Tue, 30 May 2017 15:47:14 GMT, Sönke Ludwig wrote:
But in general, the only thing that really helps (because for a concurrent GC, memory will soon become an issue) is to avoid GC allocations or dynamic allocations in general as much as possible. The
vibe.webpackage is not quite there yet, but the goal is to eliminate all dynamic allocations there eventually. This would then leave just the application logic itself for a typical web application.
That would be nice. For a web server the bump the pointer allocation strategy at least sounds like a perfect fit. Since most allocation will be request local and at the end of a request it can just reset the pointer and reuse the memory. Although the fibers complicated this a bit.