Re: [Owfs-developers] Questions about owlib implementation

I got my information after a google search:
http://www.linuxbrit.co.uk/tips/#mem_usage

Paul

On Sun, 2003-09-21 at 09:55, Nicolas Huillard wrote:
> I don't really know how to read those values, but we see that ow is only 
> one a the many memory consumers :
> 
>   VSZ  RSS COMMAND
> 1652  596 /usr/sbin/cron
> 1532  680 ow -d /dev/ttyS0 /home/maison/owfs/devices
> 2028  888 /bin/bash ./bin/temperature_logger
> 1328  416   \_ grep . /home/maison/owfs/links/te
> 1276  404   \_ sed -e s!.*/temperature/!update /
> 1940  456   \_ rrdtool -
> 
> As long as ow doesn't require 5MB (1.5 reasonable there), that's OK for me.
> 
> NH
> 
> Paul Alfille wrote:
> 
> > I'd like to have configurration options for cache and multithreading.
> > Both will be very memory intensive.
> > 
> > As for memory footprint. It's hard to tell.
> > 
> > owhttpd uses 584K, of which 500K is in shared memory. (Probably glibc).
> > So 84K, before owlib has been factored.
> > 
> > ow takes 456k of which 352k is shared.
> > 
> > Paul
> > 
> > 
> > On Sun, 2003-09-21 at 04:06, Nicolas Huillard wrote:
> > 
> >>Vadim Tkachenko wrote:
> >>
> >>
> >>>On Sat, Sep 20, 2003 at 06:09:49PM -0400, Paul Alfille wrote:
> >>>
> >>>
> >>>
> >>>>Are there really large savings in configuring out some devices?
> >>>
> >>>
> >>>I don't know. The code itself won't be too complex - all the configured
> >>>devices will be #ifdef'd in, it's the build infrastructure that gets more
> >>>complicated, but not unmanageably so.
> >>>
> >>>Theoretically, every single bit of memory on a target device may be
> >>>priceless. I'd rather cut some unneeded code than risk running out of
> >>>memory.
> >>
> >>We're taling about a filesystem, that is not really the most 
> >>memory/performance efficient way to talk to a serial port... If one 
> >>really want to have the lightest memory footprint, he will code a simply 
> >>ad-hoc C program with the PDK.
> >>On my point of view, the application will eat the most space : a few 
> >>daemons as Perl scripts (different tasks), cron/at jobs (ie. crond and 
> >>atd daemons + bash scripts), apache + mod_perl as the complete UI 
> >>(templating using HTML::Mason), RRDtool to store data, etc.
> >>I don't know what the lightest Linux system could be, but I bet 
> >>compiling out a device won't be the most memory gain. Simply forgetting 
> >>to uncheck PCMCIA support in the kernel (for instance) will waste much 
> >>more memory... Maybe a kernel-space owfs will drastically help on the 
> >>memory front...
> >>
> >>NH
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Welcome to geek heaven.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>Owfs-developers mailing list
> >>Owf...@li...
> >>https://lists.sourceforge.net/lists/listinfo/owfs-developers
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Owfs-developers mailing list
> > Owf...@li...
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers