You are not logged in.

#1 2010-02-08 22:46:04

DarksideEE7
Member
From: Arkansas, United States
Registered: 2009-06-06
Posts: 356

Using preload daemon to preload apps to memory

Basically I would like to know of other's results when using the preload daemon.

I'm using the preload daemon in hopes to speed up my system.  I'm running a fully updated Arch x86_64 (no testing repos)

I have it added it first in my daemons array in rc.conf.  It seems to be working according to:
sudo less /var/lib/preload/preload.state

I don't get any log output in:

/var/log/preload.log

however according to my (default) rules in /etc/preload.conf I should be using roughly 743 MB of RAM by this equation (from /etc/preload.conf):

#       max (0, TOTAL * memtotal + FREE * memfree) + CACHED * memcached

Shouldn't the memcached value be something other than %0?  I still have 2038MB of RAM free according to:

free -m

I know it should take some time for the daemon to learn my app usage and preload accordingly, but I would think that it should use more than 743MB on a 4GB system.

Thoughts?

Last edited by DarksideEE7 (2010-02-08 22:48:23)

Offline

#2 2010-02-08 22:57:26

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: Using preload daemon to preload apps to memory

By default it preloads only apps bigger than a certain size. Enable logging in /etc/conf.d and run dstat (from AUR) with -m and -topbio to check what preload does, use "echo 3 > /proc/sys/vm/drop_caches" to drop all caches.

Offline

#3 2010-02-09 01:25:44

DarksideEE7
Member
From: Arkansas, United States
Registered: 2009-06-06
Posts: 356

Re: Using preload daemon to preload apps to memory

Thanks for the info, I'll check it out.

EDIT:
I don't see any option for logging in /etc/conf.d/preload.  I added this:

LOG_FILE="/var/log/preload.log"

I still don't see anything when I tail -f the log file (even after restarting the daemon).  Is there something I'm missing?  According to the man page this is the default log path, but I suppose it's not enabled by default...


So I see that dstat is basicaly a frontend to the data from /proc/meminfo, eh?  Nice little tool, thanks!  I may set up some graphs to monitor I/O using KDE's System Monitor (great tool)


I changed memcache from 0 to 30, as I've seen that many guides report that as the default (except for the man page), but it doesn't seem that it has changed anything yet.


I'm still unable to get anything in the log file...

Last edited by DarksideEE7 (2010-02-09 02:54:23)

Offline

#4 2010-02-09 08:47:01

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: Using preload daemon to preload apps to memory

Set PRELOAD_OPTS to verbose 10.

Offline

#5 2010-02-09 08:48:11

DarksideEE7
Member
From: Arkansas, United States
Registered: 2009-06-06
Posts: 356

Re: Using preload daemon to preload apps to memory

All right I'll give that a shot.  Thanks smile

EDIT:

That did it!  You know it would be nice if they mentioned that little nugget in the man page in the logging section.

Last edited by DarksideEE7 (2010-02-09 08:50:03)

Offline

#6 2012-01-12 16:57:49

fsckd
Forum Fellow
Registered: 2009-06-15
Posts: 4,173

Re: Using preload daemon to preload apps to memory


aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Offline

Board footer

Powered by FluxBB