How long does OptimumCache take to initialize?

[troy.leaver]

Ive just installed OptimumCache on a server to give it a try. The terminal session timed out before it finished going through /home, (yes I *should* have used screen), but there is a /usr/sbin/optimumcache_s has been running now for a good six hours. Is that indicative of the process still running, and should it take this long? Its a four core 16GB server that runs really well/fast, and even with optimumcache_s consuming 50-100% CPU the load is okay (though higher than normal), but I would like some assurance that its still running my "optimumcache mark --recursive /home" command versus being some sort of hung process.

[iseletsk]

There is a straightforward way to differentiate "optimumcache mark --recursive /home" task from optimumcache_s resident daemon:

# ps -f -C optimumcache_s

gives stats on the daemon, which is responsible to cache what have been "marked" for caching earlier.

# ps -f -C optimumcache

gives stats on "optimumcache mark --recursive /home" task is running, if any.

High CPU consumption is known caveat of using optimumcache for some deploys. We are working on this problem.

[ray]

> High CPU consumption is known caveat of using optimumcache for some deploys.

Are you referring to high CPU during initialization only or as a constant state during normal operation?

[iseletsk]

I am refering to normal operation -- in some particular situations. We should have a patch for that soon.

[jaroslav]

So if I see this:

# ps -f -C optimumcache
UID PID PPID C STIME TTY TIME CMD
root 326830 326829 1 02:34 ? 00:05:34 /usr/bin/optimumcache mark --recursive /home
root 714484 714483 44 09:42 ? 00:00:01 /usr/bin/optimumcache stat --yaml --brief

it is normal? it is just initializing yet?

Thanks

[bogdan.sh]

Yes, most probably its normal. Just be sure to use latest optimumcache package. Time depends from used space and from current server load (it is put to sleep if LA is high etc.)