Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119957 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 18456 invoked from network); 12 Apr 2023 14:04:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Apr 2023 14:04:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id F20B81804C6 for ; Wed, 12 Apr 2023 07:04:41 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 12 Apr 2023 07:04:41 -0700 (PDT) Received: by mail-wr1-f49.google.com with SMTP id g5so14410453wrb.5 for ; Wed, 12 Apr 2023 07:04:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681308280; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ISmpE3XicYoou+BZvmSIwvf6jyT1p0tSo1x94ftKhI4=; b=lFLfJVIbwscpLKWiEOplpMZ4zKC5fHCxway668VtioQtcbe9ASGvWjMphQ+gkaN5Eo Nsw9RYRp9qZoKSbKB7eRjSzS3FDG2bpdwuOWbiDbtijDfAYDjvAZ+snchM0mdZLO4qoR 32ugUJKO5Kw2IwWJP2P7gZYy8y4LaSkDIERj4hAQKDbRosOcUjdBeSUATHAqc4+0QTzd GiTDC3KumyGootAfBEdBt2CVIbJnPctp2PaqzyDfeTHX2NkfSl72OBPEH2HVB6z5whOv Xxj9EK1QDxSzBDn90a9Vf8mpNdyEZEKZDAVd/ERz5a40GyXUruk7ntNUhhS4JcO0dYCq hwJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681308280; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ISmpE3XicYoou+BZvmSIwvf6jyT1p0tSo1x94ftKhI4=; b=M4T9KlPg0bOXWhU89mSPh70GZAHzPZwQgogDHi1CXINqdvlo+p0zCzL1TK1GTqCgnc kPxUJU2H5+4zurjHXo9snISvMVjsAtzbmXqb2VXq/v1d+15T57YDF9euRMZQbsojLJEb BFTA7l0Jfe7IyvNGEWllx2mGVPIt8P9Sp2xYodnQqbH4tGzUuU+WJtNjKWcIg6iNMSll cNYI25F27P76k5Psq/ZKrxR1t/U9QYy/gJ9JzXWHC0quS0Q/BwJnBx+HqA3KEhidPpE7 GfMo0xh1td43IcUSLlznlKD0LT61azMfZ95YYLQRKozLU5sdntHIbG5eNBuxLL9ACvVe hc4w== X-Gm-Message-State: AAQBX9ehohO1DOqIecGFqnJHqYd4vmjUcJKDLNXmlRh4vN4BCydh7j7m mEZbvQvOyVes+q1sqR+Scq078+rGF+Ahz+WvlIALaFyOAUU= X-Google-Smtp-Source: AKy350YoMkr8dNPIxOx1ZwNIP8rRY2dQrLV6kz9LJ0mIROReW/n7oGfqJJr8idzd1NXdmx4dTzi2BQGbp7MsVwp/LqA= X-Received: by 2002:adf:fecb:0:b0:2e5:18d6:8648 with SMTP id q11-20020adffecb000000b002e518d68648mr3277799wrs.6.1681308280074; Wed, 12 Apr 2023 07:04:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 12 Apr 2023 15:04:28 +0100 Message-ID: To: Herbert Groot Jebbink Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="000000000000cab65d05f9241685" Subject: Re: [PHP-DEV] Re: Possible RFC: $_SERVER['REQUEST_TIME_FLOAT'] From: rowan.collins@gmail.com (Rowan Tommins) --000000000000cab65d05f9241685 Content-Type: text/plain; charset="UTF-8" On Wed, 12 Apr 2023 at 13:25, Herbert Groot Jebbink < herbert@groot.jebbink.nl> wrote: > fallback for REQUEST_TIME and REQUEST_TIME_FLOAT to hrtime seems not > possible, hrtime is not based on the actual time, hrtime can be used to > calculate a duration or so, not to retrieve the actual time itself. > Fair enough, but that makes my first question all the more important: are there any situations or platforms where generating an hrtime value for every request would have a performance penalty? How does that performance (for everyone) compare with a single call to microtime(true) in your application to calculate the duration from REQUEST_TIME_FLOAT to start of profiling, with all subsequent profiling using hrtime? Regards, -- Rowan Tommins [IMSoP] --000000000000cab65d05f9241685--