Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66146 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16038 invoked from network); 22 Feb 2013 00:57:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Feb 2013 00:57:19 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.128.173 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.128.173 mail-ve0-f173.google.com Received: from [209.85.128.173] ([209.85.128.173:55822] helo=mail-ve0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7D/0B-58335-D62C6215 for ; Thu, 21 Feb 2013 19:57:18 -0500 Received: by mail-ve0-f173.google.com with SMTP id oz10so118821veb.32 for ; Thu, 21 Feb 2013 16:57:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=YjueqiT0TPbHNlATWWeB2lYZOBLwujhjpwgVIjG0bpU=; b=bg6wkq8jDNwR6zFSbggmMBqkREA6XSC7e0qdj68vtGYi4oioLxF0VvtSGbx0xhsGf7 l3ilDYA422Bj2+4onNUhIZbWwnwjyPz+mMTOxo0ajwk4HHthW35aEFnpbAg+EY47fMCk KwmrxllKFGYjvv6VqGxefrkG/pLrfXYu6u7uYvt5HwegKWr1c+uFZPmA4ShtittzPAGk Nh+cOOFZ/PDLoSGWNEOn0DuDEY0JgKConmd8sdzRUXCJVXmK7yJTAUH9+QRZrs6cvgji xy3EoT4i1CXS/a3tzjT+X1Qur1s17FEmkkFUqJnoOnJTK9U5SOJH41Dt+E9gtp1LJCuf NNZw== X-Received: by 10.220.154.148 with SMTP id o20mr72022vcw.54.1361494634274; Thu, 21 Feb 2013 16:57:14 -0800 (PST) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id h11sm938671vdj.12.2013.02.21.16.57.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 16:57:13 -0800 (PST) Message-ID: <5126C267.2000806@lerdorf.com> Date: Thu, 21 Feb 2013 16:57:11 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Terry Ellison CC: Brendon Colby , "internals@lists.php.net" References: <51229088.90306@lerdorf.com> <5122DA51.6090606@sugarcrm.com> <5122DBA9.2010004@lerdorf.com> <5122E00F.80409@sugarcrm.com> <5122E451.1040308@lerdorf.com> <5126B009.4090203@lerdorf.com> <5126BE9D.2060507@ellisons.org.uk> In-Reply-To: <5126BE9D.2060507@ellisons.org.uk> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkK5UdemKT+14R11sgdXzJYtRqPcwg5glctmE9Mc0GDBwsFQO9wkL1nbQeGClLQHJwcmx9z Subject: Re: [PHP-DEV] PHP causing high number of NFS getattr operations? From: rasmus@lerdorf.com (Rasmus Lerdorf) On 02/21/2013 04:41 PM, Terry Ellison wrote: > On 21/02/13 23:38, Rasmus Lerdorf wrote: >> On 02/21/2013 03:15 PM, Brendon Colby wrote: >> >>> NFS is so common for sharing files that saying "Wow, people are still >>> serving web files over NFS?" is like saying "Wow, people are still >>> using the ls command to list directory contents on Linux?" I think NFS >>> is still very widely used, even for sharing web files. >> This is simply not true. I do have a fair bit of experience in this >> field, and I don't know of any major sites that do this and I have >> worked with a good chunk of the largest sites out there. > Eh??? Fortune 500 enterprises and governmental departments are pretty > conservative. NAS and SAN based iSCSI and FCoE based elastic block > storage give great performance for server-specific file-systems, but > Brendon is right: for distributed file systems, NFS and CIFS still > dominate. By major I meant traffic-wise, not Fortune-500, although there are some of those on the list too. I mostly work with medium-to-large scale Internet companies. Think Yahoo, Facebook, Flickr, Digg, Etsy, WePay, Room77. These types of companies would never consider serving all their Web traffic from NFS. Yes, Yahoo had a ton of Netapp filers as well, but this was for shared data storage, they would never consider putting their application logic on them. This is also something that has been like this for 10+ years and nobody has stepped up to fix it so far. It shouldn't be news to anyone that stats and opens over NFS are slow. I am not sure why it should suddenly be an urgent problem for us at this point. But like I said, we may get to it. If the integrated opcode cache happens it becomes easier to manage the flow between the compiler, the cache and the executor and we can probably optimize some things there. And as I mentioned in another thread, let's see some RFCs proposing how to fix some of these things rather than simply posting "I wish the PHP devs would do this.." type of messages. These go over really badly with most of the longtime contributors here and they even tend to have the opposite of the desired effect. -Rasmus