Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65883 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60292 invoked from network); 15 Feb 2013 20:37:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2013 20:37:54 -0000 Authentication-Results: pb1.pair.com smtp.mail=keisial@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=keisial@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.176 as permitted sender) X-PHP-List-Original-Sender: keisial@gmail.com X-Host-Fingerprint: 74.125.82.176 mail-we0-f176.google.com Received: from [74.125.82.176] ([74.125.82.176:55471] helo=mail-we0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7B/F7-06160-2AC9E115 for ; Fri, 15 Feb 2013 15:37:54 -0500 Received: by mail-we0-f176.google.com with SMTP id s43so3115061wey.21 for ; Fri, 15 Feb 2013 12:37:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BSZ+c3wiB7+vamBJuXB32e3NB7ixq7af61jlJ6b1slg=; b=d3kNQXXHeAneqDa36TtDgimfNtuXzVTPLr03S0j5PZhyP6aGDb4wGbayvmQ27BGhb/ K85x1j2HNgy4t1rsrJZW1S+q1c7hS2lur/cUyJq1yypO9s9zzA8yC79AcD/R0r+cw5qS YUGVxX11ObXnAVHndji7kwWeiy7cDoF7WDlaISCT9LJq5CgLb/UHmGjtgtra6HrvT4FD uZfcePpvqfEEmNqADNP7QKYDVr1alkjKHEeDbZynHjGArEjt8FDk5jOySdtbuD3qso0W WYwfmWYxcxiufzfBs9wJjDrTLuvrw4vKTzWhUpEMghxv1rti6mye8jrXh5+OGyZGfs3c Q1nA== X-Received: by 10.180.97.197 with SMTP id ec5mr8481018wib.1.1360960671294; Fri, 15 Feb 2013 12:37:51 -0800 (PST) Received: from [192.168.1.26] (16.Red-83-52-184.dynamicIP.rima-tde.net. [83.52.184.16]) by mx.google.com with ESMTPS id gy2sm7489227wib.3.2013.02.15.12.37.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 12:37:50 -0800 (PST) Message-ID: <511E9C2C.8030000@gmail.com> Date: Fri, 15 Feb 2013 21:35:56 +0100 User-Agent: Thunderbird MIME-Version: 1.0 To: Paul Dragoonis CC: Damien Tournoud , Pierre Joye , Jan Ehrhardt , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: O+ 1st results From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=) On 15/02/13 10:25, Paul Dragoonis wrote: > On Fri, Feb 15, 2013 at 9:23 AM, Damien Tournoud wrote: >> On Fri, Feb 15, 2013 at 9:54 AM, Pierre Joye wrote: >>> no, MediaWiki caching modules only support APC or Wincache so far. >> As far as I understand, O+ doesn't have any user caching support, right? >> >> So the comparison needs to be with user caching disabled in Mediawiki >> when running with APC or Wincache. > Hi Damien, > > No, O+ doesn't have user level caching, it's only for opcode caching. It > was discussed that APC should continue to provide user level caching. Does that mean that MediaWiki was using O+ for opcode cache and APC for user level cache? The best way to compare them would be to test both opcode caches with a memcached server. No interaction between extensions, and no difference in the connections to access the caching store. Moreover, if you are using a production setup with multiple servers, you need to use memcached.