On 05/04/2011 08:17 AM, David Lehman wrote:
> On Tue, 2011-05-03 at 22:23 -0700, John Reiser wrote:
>> One guess for needing so much RAM is that the installer's allocator
>> (python/C memory manager) never reclaims anything unless forced.
>> The amount of memory _apparently_ required increases package-by-package.
>> [snip]
> A nice theory, but it shows that you have no understanding of how
> package installation works. [snip]
I measured [heap].Size for anaconda 15.30 installing Fedora-15-x86_64-DVD TC1.
kB progress
------ --------------------
14908 pre-release_warning
14908 storage-devices
17424 fresh-install
17424 hostname
18620 timezone
18744 root-password
18744 kind-partitions
20884 boot-loader
37828 install-flavor
56964 installation-starting
162644 1 minute into packages
170368 2 minutes into packages
174600 3 minutes into packages
178248 4 minutes into packages
183204 5 minutes into packages
183964 6 minutes into packages
185380 7 minutes into packages
186004 8 minutes into packages
186932 9 minutes into packages
187012 10 minutes into packages
187512 11 minutes into packages
187880 12 minutes into packages
188796 13 minutes into packages
190112 14 minutes into packages
190436 15 minutes into packages
190436 16 minutes into packages [done]
So anaconda's heap grew monotonically by 27MB over 1205 packages,
which is an average of 22kB per package. My guess was spot-on.
Also, the heap grows about 100MB for "installation starting".
Both amounts exceed 1% of 1GB system RAM with no swap space,
and deserve further investigation.
-----ps-smaps.sh
mkdir -p $1
cd $1
ps l >ps.out
for pid in $(awk '{print $3}' < ps.out); do
cp /proc/$pid/smaps $pid.smaps 2>/dev/null
done
----- top-level during package install
while true; do
date=$(date "+%H%M%S")
sh ps-smaps.sh /tmp/smaps/$date
sleep 60
done
-----
--
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
