Current time: 03-07-2021, 12:25 AM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Combination of edge cases triggers ~200ms delay in TTFB
10-28-2014, 05:39 AM
Post: #15
RE: Combination of edge cases triggers ~200ms delay in TTFB
I've been running ( LOTS ) more tests against our private instance to narrow this down more.

After trying several different options I settled with adding "gzip_min_length 1603;" to the Nginx config. I was able to get a better TTFB for both of my initial tests:


I've got another test that looks like requesting two resources. That ran into the same ~200ms TTFB delay as well, even with "gzip_min_length 1603;" set. The second request was not delayed, even though it was also for a very small file.

In the two request case it came down to the first request being less than 1,009 bytes triggering the delay:

- 2 req, 1008 byte 1st (delay):
- 2 req, 1009 byte 1st (no delay):

I tried shrinking small.html by a few bytes and increasing small.css by the same amount. Still triggered the delay:

The first request still appears to be the key here. And the 1603 limit isn't sufficient, because files below 1,009 bytes also triggered the delay.

At this point it looks like we could avoid the delay by doing the following:

- Add "gzip_min_length 1603;" to Nginx config
- Make sure all files are 1,009 bytes or more

At best these are hacky work arounds. And I'm not even 100% sure if 1,603 and 1,009 are consistent points, or just artifacts of my particular test setup.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Combination of edge cases triggers ~200ms delay in TTFB - josephscott - 10-28-2014 05:39 AM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)