Hi all
Is there a recommended apc.stat setting for Mediawiki? I've read all the apc.stat=0 (production) vs apc.stat=1 (development), but is there any hard data on the impact of =0 vs =1?
What I'm finding is LocalSettings.php can live for 40 mins, sometimes 2 hours before any changes are noticed to the file. Is there a recommended setting for a MW install?
Thanks Tom
Hi Tom,
I believe the ideal solution would be to set apc.stat to 0, and to call apc_delete_file on LocalSettings.php after an update.
Regards, -Kudu.
On 11/25/13 9:50 AM, Tom Hutchison wrote:
Hi all
Is there a recommended apc.stat setting for Mediawiki? I've read all the apc.stat=0 (production) vs apc.stat=1 (development), but is there any hard data on the impact of =0 vs =1?
What I'm finding is LocalSettings.php can live for 40 mins, sometimes 2 hours before any changes are noticed to the file. Is there a recommended setting for a MW install?
Thanks Tom _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Nov 25, 2013, at 6:11 PM, Kudu kudu@riseup.net wrote:
Hi Tom,
I believe the ideal solution would be to set apc.stat to 0, and to call apc_delete_file on LocalSettings.php after an update.
Thanks Kudu
I guess I could script that then call it with the command line after a file change.
I'm a bit concerned abt pushing out a update and changing many files when the need arises. The update script will use the actual new files and update the database schema. Do you know if there's a command to flush all files?
I guess I could restart Apache but that doesn't seem like a graceful way to handle this.
Tom
Or actually I could just call apc_delete_file from the commandline without even using a script.
Tom
On Nov 26, 2013, at 10:54 AM, Tom tom@hutch4.us wrote:
On Nov 25, 2013, at 6:11 PM, Kudu kudu@riseup.net wrote:
Hi Tom,
I believe the ideal solution would be to set apc.stat to 0, and to call apc_delete_file on LocalSettings.php after an update.
Thanks Kudu
I guess I could script that then call it with the command line after a file change.
I'm a bit concerned abt pushing out a update and changing many files when the need arises. The update script will use the actual new files and update the database schema. Do you know if there's a command to flush all files?
I guess I could restart Apache but that doesn't seem like a graceful way to handle this.
Tom _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org