Re: Fancontrol memory consumption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 02 Mar 2015 12:05:09 +0100, Taz wrote:
> Le 02/03/2015 11:30, Jean Delvare a écrit :
> > On Thu, 13 Nov 2014 15:36:32 +0100, Taz wrote:
> >> (sorry I just saw my reply still was in my drafts, don't know why...)
> >>
> >> Indeed : my current bash version is 4.3.11
> >> Although I don't have line 585 in my fancontrol script
> >> I can apply the the patch (lines 497 & 536 for fancontrol v0.7)
> >>
> >> I also gave it a try without the wait lines and not sending to
> >> background the previous
> >> sleep command the wait was waiting for anyway (useless ?)
> >>
> >> => Mem consumption seems to be the same in all cases, we'll see in the
> >> long run...

I don't think you ever reported the results of that test? With the
first patch applied, does fancontrol still reach 25 MB of memory over
time, or not?

> > BTW, can you please tell me
> > * Which architecture this is (x86 or x86-64)?
> > * The value of "ulimit -u" on this system.
> > * The total amount of memory on the system.
> >
> > As Chet Ramey explained to me, the memory consumption is bound and the
> > default limit depends on these factors. Assuming an x86-64 system,
> > eating 22 MB of memory as you reported would take about 734000 records
> > of 32 bytes each, and "ulimit -u" would be set to that value by default
> > for a system with about 187 GB of memory. Which I would not expect in a
> > NAS, so something is wrong.
> >
> 
> The hardware is actually a ReadyNAS ultra 6000 with 2GB RAM.
> I'm running a x86_64 ubuntu server 14.04 with 3.16 SMP kernel
> and fancontrol from standard repos (pkg vers is 1:3.3.4-2ubuntu1).
> 
> =======
> 
> (root@ReadyNAS:pts/0) # ulimit -u
>      7892
> 
> (root@ReadyNAS:pts/0) #free
>                   total       used       free     shared buffers     cached
>      Mem:       2039828    1829656     210172        708 4796    1091516
>      -/+ buffers/cache:     733344    1306484
>      Swap:      5242876          0    5242876

This seems totally reasonable. With theses settings, bash should not
consume more than 247 kB of memory to remember the process statuses.
This can't explain the 25 MB you reported initially.

So I start suspecting that your problem is different from the "wait $!"
issue I have been investigating so far. I could reproduce the memory
increase caused by "wait $!", but I could never get bash to reach 25 MB
as you reported.

So maybe it's a different bug. bash 4.3.11 is getting old, there have
been 22 upstream fixes meanwhile (latest stable version is 4.3.33.)
Maybe a more recent version is available for your system now? This
could also be a bug specific to the Ubuntu bash package you're running,
who knows.

-- 
Jean Delvare
SUSE L3 Support

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux