On Wed, Feb 17, 2016 at 1:35 PM, Avi Kivity <a...@scylladb.com> wrote: > We are using systemd to supervise our NoSQL database and are generally > happy. > > A few things will help even more: > > 1. log core dumps immediately rather than after the dump completes > > A database will often consume all memory on the machine; dumping 120GB can > take a lot of time, especially if compression is enabled. As the situation > is now, there is a period of time where it is impossible to know what is > happening. > > (I saw that 229 improves core dumps, but did not see this specifically) > > 2. parallel compression of core dumps > > As well as consuming all of memory, we also consume all cpus. Once we dump > core we may as well use those cores for compressing the huge dump. > > 3. watchdog during startup > > Sometimes we need to perform expensive operations during startup (log > replay, rebuild from network replica) before we can start serving. Rather > than configure a huge start timeout, I'd prefer to have the service report > progress to systemd so that it knows that startup is still in progress.
Hi. Similar topic from the past - https://lists.freedesktop.org/archives/systemd-devel/2015-March/028919.html. Though, I believe this is an architectural problem than real necessity. Umut > > Hope this is useful, > > Avi > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
