On Sun, Dec 09, 2018 at 07:45:08AM +0100, Andreas Tille wrote: > there are some new upstream versions out now. I wonder whether this > is fixed now. Please can you give advise how exactly measure this > number. I admit I do not understand what you mean by > > as measured by Committed_AS in /proc/meminfo
Hello Andreas. It means I do this: grep Committed_AS /proc/meminfo to see how much memory I need. I first measure it before the build begins, and then I measure it during the build and substract the initial value. This is how I try to estimate the amount of memory required to build a given package. In this case (python-ruffus), it used to be 18 GB for version 2.7, which made it to be the most memory demanding package in buster so far. Now in version 2.8.1-3 and 2.8.1-4 I get 38 GB which is a lot worse. A simple loop like this during the build will work: while true; do grep Committed_AS /proc/meminfo; sleep 1; done Thanks.
