Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115960 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 80598 invoked from network); 6 Sep 2021 10:36:56 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Sep 2021 10:36:56 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7BFFC1804BE for ; Mon, 6 Sep 2021 04:14:07 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 6 Sep 2021 04:14:06 -0700 (PDT) Received: by mail-wm1-f49.google.com with SMTP id k5-20020a05600c1c8500b002f76c42214bso4677093wms.3 for ; Mon, 06 Sep 2021 04:14:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hXoiOxPQDA7JJ1R7DFBqAQk7kUfJ2XJdeIVJVk+gmVs=; b=TMZbjIIi1hK3rL5+25B9qKNNE7k/3LkDdZk/x2ivt1b9LkjUnM33eC7OXndRInOCoz E67WzygdqJT/JkcPkMhiJ3g5vtAwkSMwsOXtIXH+bmCoCJP1AOnNq+w9amYPxFZLSjPU YinWO60IqoMmd3V7CgGxAVR5EGVZ3jTyohvTS0J4qUrlkuTnxYH5a6HsH0MfpTVlEc+0 cTn7ddzmUKWSjDHOXgce5zcJTgTVw7HO6NQpJcfpvgZTuCScxzkli2WR1tE6u2NWQXV1 4T9VF7YYZJe01fyjM7tWj7x+6v0gRquf6k5mOnL6nv/tgnis+rP5aab/F0nQg6SgX4D5 9z7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hXoiOxPQDA7JJ1R7DFBqAQk7kUfJ2XJdeIVJVk+gmVs=; b=j3ZB412f/8tu8Nu77Jv5FD4752rWd160pbqAQ55XES5j3YM+MO1Z20YK538ZiH5ZA5 ZxUWWD6C6A9HR5YMYjcD8c+tN2uNgkWbs1QK4jx+7F5dSpp23wVGoxYxAiR1W33e6KsX KqL49QJ/xcCrjWlm4hdKZ00GALaGlg/jlg8afie7NhFcQSSoYDrMfiuQcdsHyqDmKbGJ 3Gmvl8zxH7n5SGwW/rPMvvuDW3Uj2a+KUSXLhgW7hYDwCfSzHoqy1BNJDPd8KL8+K4/Q CdCWZXAJZoK7MXWlIVWhyBTwltPV1aKph5UUogBK0GffZlsKAq1k1OFC7H2GHgMz9UJI W3oQ== X-Gm-Message-State: AOAM532775YZ9KRmrtw2S/N5yAIEhSOoydgF6JG8061CPs7j/nuDFBov zFrL6EBtMPeZq1jDt6cZx0/1Zt6R2xGlw5eWENiWcg== X-Google-Smtp-Source: ABdhPJzVE8rTwpOlWOKGZcNeVXqJhKhRgPYzd+veLFf7Qh5YT8TMD7lIKIVddog1XmlMB6jfg8c4XYmgXIZXMiqUMM4= X-Received: by 2002:a1c:2090:: with SMTP id g138mr11028044wmg.98.1630926845550; Mon, 06 Sep 2021 04:14:05 -0700 (PDT) MIME-Version: 1.0 References: <0A048A30-444F-4DB0-A79C-9EA9BD07B1EC@cschneid.com> <569E3A48-E3F5-46FA-BA08-D2493CE4FD33@cschneid.com> <9B6A493C-DBA6-4CF0-9AE2-DAA0A700A7D2@cschneid.com> In-Reply-To: Date: Mon, 6 Sep 2021 13:13:54 +0200 Message-ID: To: Hans Henrik Bergan Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000048b7d505cb51bff1" Subject: Re: [PHP-DEV] Adding a way to disable the stat cache From: kontakt@beberlei.de (Benjamin Eberlei) --00000000000048b7d505cb51bff1 Content-Type: text/plain; charset="UTF-8" On Fri, Sep 3, 2021 at 11:51 PM Hans Henrik Bergan wrote: > PS i've seen *HORRIBLE* fs performance for php-running-on-windows, > where the same filesystem operations on the same files took like 5 seconds > on linux-running-on-vmware-on-laptop-running-windows-10, versus several > minutes for the same operation on the same laptop on windows 10 directly.. > for people looking for best-case-scenario for the stat cache, try looking > at windows fs performance.. (if anyone even cares about that? i personally > don't, i never run anything performance-sensitive-php code on Windows, just > noticed horrible fs performance in the past) > The stat cache does not necessarily solve this issues though, only in very limited cases where you work with the *same* file over and over again. The stat cache only ever has exactly one entry, the *last* file that was accessed. So if you work with many diferent files the stat cache does not do what you would expect, to store the information of all these files. It overwrites the cache with a new file entry when its not the same file as currently stored. > > On Fri, 3 Sept 2021 at 22:22, Kevin Lyda wrote: > > > On Fri, Sep 3, 2021 at 9:12 PM Christian Schneider > > wrote: > > > I'm interested in the load put on a system with a high request count > and > > a typical application. > > > Reducing system calls used to matter there as the kernel does not > > multi-process the same way user land does. > > > > > > But then again, maybe I'm overly cautious :-) > > > > This PR allows people to do just that experiment. > > > > Kevin > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: https://www.php.net/unsub.php > > > > > --00000000000048b7d505cb51bff1--