Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65921 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82464 invoked from network); 19 Feb 2013 02:14:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2013 02:14:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.139 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.139 smtp139.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.139] ([67.192.241.139:46509] helo=smtp139.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 80/B8-34654-210E2215 for ; Mon, 18 Feb 2013 21:14:43 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp30.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 2191B3481A7; Mon, 18 Feb 2013 21:14:40 -0500 (EST) X-Virus-Scanned: OK Received: by smtp30.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id C7489348141; Mon, 18 Feb 2013 21:14:39 -0500 (EST) Message-ID: <5122E00F.80409@sugarcrm.com> Date: Mon, 18 Feb 2013 18:14:39 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Rasmus Lerdorf CC: "internals@lists.php.net" References: <51229088.90306@lerdorf.com> <5122DA51.6090606@sugarcrm.com> <5122DBA9.2010004@lerdorf.com> In-Reply-To: <5122DBA9.2010004@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP causing high number of NFS getattr operations? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yeah, but NFS, especially without the realpath cache, which you lose if > you turn on open_basedir, is deathly slow because of all the stats. > > Typically PHP scripts are not actually "writable files" and the way to > keep them in synch across multiple machines is to use a deploy > mechanism/rsynch to deploy them. You may very well have some writable rsync may be way too slow if you need the change appear more or less "immediately" on all servers. Unless you run rsync each second if which case you're probably better off with NFS :) > files that need to be shared at the app-level, but then we wouldn't be > talking about PHP stat calls and the realpath cache. And most people You would still if the data is stored as php file. Which last time I tested - given APC or something like - was the fastest way to get a bunch of data into PHP (it was faster than loading and unserializing, even with APC/memcache). > have moved to something like memcache for sharing writable data across > machines. memcache is non-persistent. It's a cache, not a storage solution, so you can not use it for anything that actually needs to be stored permanently. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227