by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 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,sftp

Use Laravel's Storage SFTP Drvier for remote file upload

Why do I separate the front and back of the website? My idea is very simple, that is to rely on a set of background to control all the website data in the foreground. Assuming that the front-end website is a pure marketing website, it is nothing more than the subject content, just like the article above, without any particularly complicated logic. Therefore, it is enough to set up the backend database and connect different frontends. Then there is the last question, how can my backend HTML editor post pictures directly to the frontend? Laravel's Storage SFT Driver is a good antidote.

linux

Multiple ssh configuration files for public key authentication

When we use ssh public key authentication, we usually add relevant settings in ~/.ssh/config. If some are used by the company or at home, can multiple configs be used? In fact, it is possible. We can use git to load the company-shared, version-controlled config through Include.

d-laravel,docker

D-Laravel v1.2.1 version change description (recommended update, must avoid stepping on thunder)

D-Laravel v1.2.1 revision instructions use GuzzleHttp\Client; When posting, there is an access denied problem. If you are upgrading from an older version, you may need to adjust the configuration file in etc/default-ssl.conf (if there is one) Please adjust php:9000 to web:9000, you can adjust it by executing ./console secure once. In the docker-compose configuration file, change the PHP-FPM container to network_mode: "service:web"...