by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 years ago )

About TTFB:

TTFB(Time To First Byte): The browser is waiting for the first byte of the response. TTFB stands for time to first byte.
This time includes 1 round trip delay and the time for the server to prepare a response.

Key points:

Okay, maybe everyone will wonder that the TTFB time of your host is very long, which means that the host may perform some calculations before the screen can be displayed.
For example, a large number of database queries, or the network is too slow, and other factors, but how to judge?
We can compare whether the HTML static page is very different from the simple PHP dynamic page, and perhaps find out the problem of slow TTFB response.
For example, if the TTFB is 16ms on a static page but when it comes to a dynamic page in PHP, it runs 3xxms without any calculation.
Such a problem may be in the setting of PHP.

You can see if any plug-in is affected, such as Xdebug plug-in with PHP enabled,
At this time, the TTFB will not be 13.36ms below, but may become 2xxms.

So if it is the Porduction version, and Xdeubg is used in php.ini, remember to disable the Xdebug function.

Tags:

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


Laravel,artisan

About the operation of --env in Laravel's artisan

This article uses Laravel 9.40.1 for operation. I believe many people know the usage of --env, but I still provide some information for Laravel beginners. In the artisan command, we can use --env to specify different .env files, so that under different subdomains, I can use different environments or even different databases. You should have also noticed that this site uses a multilingual environment, do you write two sets? Of course not, basically I created multiple .env in the same Project.

jenkins

How to use Gogs to trigger Jenkins to test and deploy Pipline

How to use Gogs to trigger Jenkins to test and deploy Pipline. http://{USER}:{API_TOKEN}@{JENKINS_URL}/job/{JOB}/build?token={AUTHENTICATION_TOKEN}

composer

How do you know where the directory of your composer environment is?

Check the composer home directory of your own environment