Nginx, from connected to first byte

Server NGINX
1

i set up a nginx server with php fastcgi last month, but i found a
little problem with it.
my frontpage is loaded in 8-10 seconds, but there is 7 seconds waste
from the time when connected server, to the time when start to send the
first byte. the real time which is used by the process of connection and
transmission is short, i can’t find a solution, could anybody help me?

Posted at Nginx Forum:

2

On Mon, Mar 14, 2011 at 10:09:15AM -0400, digginchina wrote:

Hi there,

i set up a nginx server with php fastcgi last month, but i found a little
problem with it.
my frontpage is loaded in 8-10 seconds, but there is 7 seconds waste from the
time when connected server, to the time when start to send the first byte. the
real time which is used by the process of connection and transmission is short, i
can’t find a solution, could anybody help me?

The debug log will probably show what nginx thinks is happening during
the full 8-10 seconds. Look either side of the 7-second gap to see
whether you are better off examining nginx, the nginx-fastcgi
connection,
or the fastcgi-application interaction.

Good luck with it,

f

Francis D. [email protected]

3

hi Francis,
thanks a lot for the reply, i disable debug when compile the nginx, need
i re-compile? i don’t know the exact meaning of “debug log”, whether
it’s a general nginx log or another log? and one more question, how to
check the status of nginx-fastcgi connection and the fastcgi-application
interaction?
btw, i use unix file pid to connect fastcgi, could you please tell me
whether this method or network port method is better?
thanks a lot.
regards
solo

Posted at Nginx Forum:

4

On 15 Mar 2011 04h05 WET, [email protected] wrote:

hi Francis, thanks a lot for the reply, i disable debug when compile
the nginx, need i re-compile? i don’t know the exact meaning of
“debug log”, whether it’s a general nginx log or another log? and
one more question, how to check the status of nginx-fastcgi
connection and the fastcgi-application interaction? btw, i use unix
file pid to connect fastcgi, could you please tell me whether this
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Do you mean UNIX sockets? There’s no PID involved.

method or network port method is better? thanks a lot. regards
solo

There’s no harm in trying to use TCP sockets.

— appa

5

On Tue, Mar 15, 2011 at 12:05:52AM -0400, digginchina wrote:

Hi there,

thanks a lot for the reply, i disable debug when compile the nginx, need i
re-compile? i don’t know the exact meaning of “debug log”, whether it’s a general
nginx log or another log?

Debug log: A debugging log

Must be enabled at compile time.

and one more question, how to check the status of nginx-fastcgi connection and
the fastcgi-application interaction?

nginx-fastcgi: nginx is the client, your fastcgi server is the
server. Debug log shows the nginx side; tcpdump or something similar
can show the traffic between the two; and your server may have a “debug”
mode to show its idea of the interaction.

fastcgi-application: your fastcgi server and your application. Maybe
extra sleeps and prints can show what is going on?

btw, i use unix file pid to connect fastcgi, could you please tell me whether
this method or network port method is better?

If the fastcgi server is on a different machine, the network port method
is better because it works.

If nginx and fastcgi are on the same machine, the connection method
shouldn’t matter (much). Unix sockets should be better from an
access-control view. But there are suggestions on this list recently
that the combination of “sendfile on” and unix sockets on at least one
OS has problems with largish uploads.

The two options seem close enough to me, that if your testing doesn’t
show a good reason to pick one over the other, then choose either and
don’t worry about it.

Good luck with it,

f

Francis D. [email protected]