Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120255 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29110 invoked from network); 13 May 2023 06:27:17 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 May 2023 06:27:17 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EA811180382 for ; Fri, 12 May 2023 23:27:14 -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.3 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,RCVD_IN_VALIDITY_RPBL,SPF_HELO_NONE,SPF_NONE, 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-ej1-f45.google.com (mail-ej1-f45.google.com [209.85.218.45]) (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 ; Fri, 12 May 2023 23:27:14 -0700 (PDT) Received: by mail-ej1-f45.google.com with SMTP id a640c23a62f3a-965ac4dd11bso2138729766b.2 for ; Fri, 12 May 2023 23:27:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=groot-jebbink-nl.20221208.gappssmtp.com; s=20221208; t=1683959232; x=1686551232; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ftx5g+oVrj2AR341SNhO1pkSyJdAjZ6bTgxAFfLFTYQ=; b=tferTQlo0NDp2hzxGI0NgGlljycxiawKta/IqDaXLosfd4uTx5dQRbHvA6eLt2fUjY 3u09KFTcOl+EvZ/CzGM/O/iH50tr48hMrZcC/x+v+hkClG9qojhyTSzCAfiyl8cH+uTo OlwXUhSeE7IH2VVlpN4/zUHpUBEz2iYjR4zpl2jW13z++RFiMeR0V/krOp7Yk15sHxpl ncg4NLquiytMMVFMOXwGM1qlQdGdL+/YZlE6wOvhydG80XqyDUbCQdI0sVDFnPRMX6uY nwbEdANNKLfQAoFS3VBwbdaVP0IFKpMFV3nU/noyC0u3chSJ7hKfpcHpAJ+N9soygciB 0y1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683959232; x=1686551232; h=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=ftx5g+oVrj2AR341SNhO1pkSyJdAjZ6bTgxAFfLFTYQ=; b=fdupx2m0gd7BUv/QZk5aunO7TZHUgobgLtTo/33UXYazi3Jh+VPRyRTMqHZOmYBb8R kZ51N21Jkb+2pUHh+i20BEumLpvzg5AXOplDR5gTwy0C9ODsIPq+g+THH7UydrSTDoMJ szb6/eJoTqwNIA0yoZ1vF9kCnPuW3mr7TJ4mo4+r2IyyLF41BfkYYxZn87t9wzYflmQ5 zF0HmC2wqcwEWlZJrL5p5x9PFAcdoSPRLhKImubIKXXFu+jPFRRE/qL3HDEPqj6WLHDf PLHrZUD8IhPXw40E9wuKnmddbwnAz0W+QWyrhs/vpCRvGvADlpo4f7dwivufkpVSMWYB Ufrw== X-Gm-Message-State: AC+VfDz54gOh70bmNCp/U0VRw4XlG096obD48ZXqtWUeM4Yhyvv3www+ AA2aFxFEQNPSHDVdBzTAr6d+kxk7wjMW9XLiPSPxxaHV+rTTgcXzOLg= X-Google-Smtp-Source: ACHHUZ6iRTHlkMG5XtXzP50b3/Mz47fWw0apDJ8q9x6N1ygBx3TzKRsyWAEpxQOhCs6Je1E7Wdy9zU26LstIazFqMTE= X-Received: by 2002:a17:907:806:b0:953:47fc:3f0b with SMTP id wv6-20020a170907080600b0095347fc3f0bmr21607095ejb.53.1683959232445; Fri, 12 May 2023 23:27:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 13 May 2023 08:27:01 +0200 Message-ID: To: internals@lists.php.net Content-Type: multipart/alternative; boundary="000000000000ddceb305fb8d4f46" Subject: Re: [PHP-DEV] Re: Possible RFC: $_SERVER['REQUEST_TIME_FLOAT'] From: herbert@groot.jebbink.nl (Herbert Groot Jebbink) --000000000000ddceb305fb8d4f46 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Apr 12, 2023 at 4:04=E2=80=AFPM Rowan Tommins wrote: > 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? > Is it every request? or at the first reference to the $_SERVER super global ? But yeah, of course everything new thing does have a performance penalty --000000000000ddceb305fb8d4f46--