Am 28.04.2012 20:47, schrieb Rory McGuire:
Awesome! that was one of my concerns with D in general with server software and its long running nature. I've been thinking about fibers and socket.d this week. Glad you anounced this before I started working on something :D.
Yeah I've also tought about this for a while before I was finally fed up with a REST-server project and finally started vibe. Of course it's much more work now in total but making web applications is finally fun now :)
How difficult would it be for you to split the async IO parts into a separate library? This would be very much like gevent (python: http://www.gevent.org/).
That would basically be vibe.core and vibe.stream. Those have no dependencies to other modules so they can already be used without the rest of the code adding overhead of any kind.
Any chance of supporting WSGI?
It's not directly planned from our side but either eventually or if someone else writes a version I think it will get in.
On Sat, Apr 28, 2012 at 2:36 PM, Sönke Ludwig <slud...@outerproduct.org <mailto:slud...@outerproduct.org>> wrote: Am 27.04.2012 11 <tel:27.04.2012%2011>:34, schrieb Sönke Ludwig: I'm starting to monitor it now. Directly after startup, the website is at 32 MB. The traffic has dropped a bit but hopefully it's enough to see something if there is a hidden leak. A mid-term test now shows that shortly after startup the virtual memory usage went up from 32MB to about 44MB. After 24h and about 50k requests it stays at 43.5MB. Real memory usage is 15MB.
