Re: Bug#24217: bigloo not stripped
Steve Dunham <dunham@cse.msu.edu> writes:
> > C) Depending on the size of the binary, not stripping it does more
> > than just take up disk space, it takes up extra swap and ram when
> > running, and potentially increases memory fragmentation and
> > decreases cache locality)
>
> This doesn't make sense to me. How does not stripping the binary make
> it take up more RAM and swap?
Given your explanation, it wouldn't. Even after a reasonable amount
of time, I'm still not entirely used to the fact that I'm now using an
OS that often does the right thing :>
I had assumed that the debugging symbols would be intermingled with
the code. In such a situation, you get deleterious effects on the
memory heirarchy (especially wrt cache locality). If things are
organized as you say, then that's not an issue...
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: