Dominik Vogt wrote:
> Any decent kernel is clever enough not to load multiple copies of the
> same write-only data.
I'm using the linux kernel, 2.4.21.
Results of the "free" command with 100 instances of FvwmPager running:
total used free shared buffers cached
Mem: 224728 131148 93580 0 0 18396
-/+ buffers/cache: 112752 111976
Swap: 51192 1372 49820
And the same after "killall FvwmPager":
total used free shared buffers cached
Mem: 224728 70896 153832 0 0 18416
-/+ buffers/cache: 52480 172248
Swap: 51192 1372 49820
I guess that with 'a few hundreds' per module te amount of memory freed
after killing all those pagers should change by a couple of megabytes in
worst case , not by ~60MBs. And I believe these readings are correct
- starting more modules (200 and up) chewed up all of RAM and swap, and
the infamous OOM killer started killing processes.
Either it's my config, or running two pagers uses more ram than just "(1
FvwmPager) + (less than 1KB)"
>> And fvwm modules are quite big already.
>
> Try
>
> $ make install-strip
I meant the memory usage, not executable size (and debug info never gets
loaded while executing a binary (except for running under debuggers),
right?)
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
