Am 25.10.2016 um 15:24 schrieb Mario Silva:
Hello,
When we start our servers based on vibe.d everything starts with a pretty small memory footprint and everything is pretty fast like expected.
However, after a while, typically a couple of hours but not always, our servers start swapping until a tool of ours which keeps pinging the servers times out and simply restarts the instances restarting the cycle - everything pretty fast, starts swapping, slow, restarted...
Anybody else with the same problem?
Trying to understand if this is a D problem, a Vibe.d problem? Our code seems to be pretty trivial, so it seems hard to be the cause of the problem :(This problem used to be a lot worse, but on DMD 2.067 when the https://issues.dlang.org/show_bug.cgi?id=4890 bug got fixed, the problem got a lot more manageable. However, it's still not perfect and with our growth the restarts are getting a lot more frequent.
Thanks,
Mario
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.