On Wed, 26 Oct 2016 18:41:43 +0200, Sönke Ludwig wrote:

Am 25.10.2016 um 17:25 schrieb Mario Silva:

On Tue, 25 Oct 2016 16:27:35 +0200, Sönke Ludwig wrote:

AFAIK, there are currently no known leaks in vibe.d, and my own services
appear to have stable memory usage, but who knows... Can you run a "dub
-b profile-gc" build for a while, and post the profiler log? There are
parts that allocate without the GC and the profile log isn't always
particularly meaningful (re-allocations are not handled in a meaningful
way), but it should be a good start.

Hi Sönke,

I tried that command but I don't find the log anywhere.
Where is the log file going?

Thanks,
Mario

Should be at ./profilegc.log - but I just noticed that LDC doesn't
support this mode, so you need to build with DMD.

Hi Sönke,

Thanks, found it :)
I built this on my development machine and used 'ab' to make a 1000 requests to our index page with 100 concurrent requests.

It started occupying around 2.3% of memory in my machine and when I finished it was occupying 17.8%. My machine has 16GB of ram btw.

I then posted the log below but it simply discarded my message without giving me any error :( Is there a way I can send you the file other then having to copy the content here?

Thanks,
Mario