Question

I’ve recently started using APC cache on our servers. One of the most important parts of our product is a CLI (Cron/scheduled) process, whose performance is critical. Typically the batchjob consists of running some 16-32 processes in parallel for about an hour (they “restart” every few minutes).

By default, using APC cache in CLI is a waste of time due to the opcode cache not being retained between individual calls. But APC also contains apc_bin_dumpfile() and apc_load_dumpfile() functions.

I was thinking these two function might be used to make APC efficient in CLI mode by having it all compiled sometime outside the batchjob, stored in a single dumpfile and having the individual processes load the dumpfile.

Does anybody have any experience with such a scenario or can you give good reasons why it will or will not work? If any significant gains could reasonably be had, either in memory use or performance? What pitfalls are lurking in the shadows?

Answer 1

Disclaimer: As awesome as APC is when it works in CLI, and it is awesome, it can equally be as frustrating. Use with a healthy load of patience, be thorough, step away from the problem if you’re spinning, keep in mind you are working with cache that is why it seems like its doing nothing, it is actually doing nothing. Delete dump file, start with just the basics, if that doesn’t work forget it try a new machine, new OS, if it is working make a copy, piece by piece expand functionality – there are loads of things that won’t work, if it is working commit or make a copy, add another piece and test again, for sanity-check recheck the copies that were working before, cliches or not; if at first you don’t succeed try try again, you can’t keep doing the same thing expecting new results.

Ready? This is what you’ve been waiting for:

Enable apc for cli

apc.enable-cli=1

it is not ideal to create, populate and destroy the APC cache on every CLI request

   - previous answer by unknown poster since removed.

You’re absolutely right that sucks, lets fix it shall we?

If you try and use APC under CLI and it is not enabled you will get warnings.

something like:

PHP Warning:  apc_bin_loadfile(): APC is not enabled, 
              apc_bin_loadfile not available.
PHP Warning:  apc_bin_dumpfile(): APC is not enabled, 
              apc_bin_dumpfile not available.

Warning: I suggest you don’t enable cli in php.ini, it is not worth the frustration, you are going to forget you did it and have numerous other headaches with other scripts, trust me its not worth it, use a launcher script instead. (see below)

apc_loadfile and apc_dumpfile in cli

As per the comment by mightye php we need to disable apc.stat or you will get a warnings

something like:

PHP Warning:  apc_bin_dumpfile(): Excluding some files from apc_bin_dump[file].  
              Cached files must be included using full path with apc.stat=0. 

launcher script – php-apc.sh

We will use this script to launch our apc enabled scripts (ex. ./php-apc.sh apc-cli.php) instead of changing the properties in php.ini directly.

#/bin/sh
php -d apc.enable_cli=1 -d apc.stat=0 $1

Ready for the basic functionality? Sure you are =)

basic APC persisted – apc-cli.php

<?php
/** check if dump file exists, you don't want to use file_exists */
if (false !== $dump_file = stream_resolve_include_path('apc.dump'))
    /** so where were we lets have a look see shall we */
    if (false !== apc_bin_loadfile($dump_file))
        /** fetch what was stored last run just for fun */
        if (false !== $value = apc_fetch('my.awesome.apc.store'))
            echo "$value from apc\n";

/** store what gets fetched the next run just for fun */
apc_store('my.awesome.apc.store', 'awesome in cli');
/** what a shlep lets not do that all over again shall we */
apc_bin_dumpfile(array(),null,'apc.dump');

Notice: Why not use file_exists? Because file_exists == stat you see and we want to reap the reward that is apc.stat=0 so; work within the include path; use absolute and not relative paths – as returned by stream_resolve_include_path(); avoid include_once, require_once use the non *_once counterparts; check your stat usage, when not using APC(Muchos important senor), with the help of a StreamWrapper echo for calls to method url_stat; Oops: Fatal scope over-run error! aborting notice thread. see url_stat
message: Error caused by StreamWrapper outside the scope of this discussion.

The smoke test

Using the launcher execute the basic script

./php-apc.sh apc-cli.php

A whole bunch of nothing happened that’s what we want right, why else do you want to use cache? If it did output anything then it didn’t work, sorry.

There should be a dump file called apc.dump see if you can find it? If you can’t find it then it didn’t work, sorry.

Good we have the dump file there were no errors lets run it again.

./php-apc.sh apc-cli.php

What you want to see:

awesome in cli from apc

Success! =)

There are few in PHP as satisfying as a working APC implementation.
nJoy!