search for: callign

Strange because in my all my experiments calling malloc.trim always helped - memory reported by top decreased to the level it supposed to be. Do you have in mind case when calling malloc.trim won't do anything? Also shouldn't MALLOC_TRIM_THRESHOLD_ env variable has impact on malloc.trim calls? At the moment seems any value is ignored... 12 ???. 2017 ?. 6:09 ?? ???????????? "Simon

...loc1 env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1 R This does not seem to hold onto memory to the same degree, but I don't know about any other aspect of its performance. The emacs post suggests that calling malloc_trim may have more of an effect in some cases: the post describes callign it via gdb on all running processes and sees a substantial memory footprint drop for emacs, Xorg and opera. I tried the same experiment on my system with emacs, Xorg and firefox and didn't see what that post saw -- maybe 1 few percent recovery. At this point I'm not sure we have enough dat...

...act that we re-import most commits multiple times. This makes it hard to reason about how different notifications will fire, and which source will actually autoclose differential revisions. The current state is that most commits should notify the committer twice: once for the Subversion repo (repo callign rL), and once for git master (rG). I think this may actually be the best state while we're living in both worlds: the SVN commit is the source of truth, but a lot of folks care about re-syncing from Git, so that also seems like something folks will want. Of course, this is a transitional pain p...

...multiple times. This makes it hard to > reason about how different notifications will fire, and which source will > actually autoclose differential revisions. > > > > The current state is that most commits should notify the committer twice: > once for the Subversion repo (repo callign rL), and once for git master > (rG). I think this may actually be the best state while we're living in > both worlds: the SVN commit is the source of truth, but a lot of folks care > about re-syncing from Git, so that also seems like something folks will > want. Of course, this is a...

I actually run a in-house Phabricator instance with 400+ users and multiple git repo including custom extension developments I also follow the Phabricator development quite closely because we upgrade every couple of weeks I’d be more than happy to help maintain the phab instance for LLVM MyDeveloperDay On Fri, 31 May 2019 at 09:19, Manuel Klimek via llvm-dev < llvm-dev at lists.llvm.org>