Slow http responsesApache has a long lag before respondingHow to deal with slow HTTP clients?Why does wget get redirected to localhost when fetching an unresolvable page?HTTP response time profilingCURL - saving multiple HTTP responsesHTTP/1.1 Status Codes 400 and 417, cannot choose whichCould an ISP selectively block .png, .jpg, .js, .css and others from internal HTTP server?Is it bad to redirect http to https?POST request body fails to get to PHPApache 2.2.22 sporadically Changing POST requests from Safari 8,9 to GETHow to debug slow server response time?
Why is Na5 not played in this line of the French Defense, Advance Variation?
Is it okay to have a sequel start immediately after the end of the first book?
How to write a convincing religious myth?
Razzle Dazzle simulator
Can there be absolute velocity?
Was planting UN flag on Moon ever discussed?
Do you need to let the DM know when you are multiclassing?
Canada travel to US using Global Entry
So a part of my house disappeared... But not because of a chunk resetting
Are the guests in Westworld forbidden to tell the hosts that they are robots?
What would be the way to say "just saying" in German? (Not the literal translation)
If there's something that implicates the president why is there then a national security issue? (John Dowd)
The significance of kelvin as a unit of absolute temperature
Trying to get (more) accurate readings from thermistor (electronics, math, and code inside)
Diatonic chords of a pentatonic vs blues scale?
Cooling tower for nuclear power plants
Grep Match and extract
Who is "He that flies" in Lord of the Rings?
I've been given a project I can't complete, what should I do?
NUL delimited variable
Can you make an identity from this product?
Why ambiguous grammars are bad?
How to find a better angle and distance for clicking picture of a distorted artwork to achieve 3D effect?
How to get depth and other lengths of a font?
Slow http responses
Apache has a long lag before respondingHow to deal with slow HTTP clients?Why does wget get redirected to localhost when fetching an unresolvable page?HTTP response time profilingCURL - saving multiple HTTP responsesHTTP/1.1 Status Codes 400 and 417, cannot choose whichCould an ISP selectively block .png, .jpg, .js, .css and others from internal HTTP server?Is it bad to redirect http to https?POST request body fails to get to PHPApache 2.2.22 sporadically Changing POST requests from Safari 8,9 to GETHow to debug slow server response time?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am running an apache web server on debian 6.0 with kernel 2.6.32-5-amd64.
In certain times of the day, usually when more people are online, the server have very slow responses. I am sure, that is not load, it is not DB, it is not PHP, accualy this command:
time wget 127.0.0.1
is quite slow:
--2013-09-20 15:36:49-- http://127.0.0.1/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-09-20 15:36:52 ERROR 404: Not Found.
real 0m2.663s
user 0m0.004s
sys 0m0.004s
Response time is up to 5sec. The point of waiting is after "HTTP request sent, awaiting response..."
Page generating after this lag common for all http requests is fast, like 50ms.
I tested my web using http://tools.pingdom.com/fpt/, first response is always slow, most of content load is also slow but few are quite fast, but I cannot tell, if this tool have some sort of cache.
telnet 127.0.0.1 80
is fast, the response show without delay:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Where can be the problem? It must be something before the request goes to apache.
Please tell me at least about some debugging tools for this.
http debian-squeeze response-time lag
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
|
show 1 more comment
I am running an apache web server on debian 6.0 with kernel 2.6.32-5-amd64.
In certain times of the day, usually when more people are online, the server have very slow responses. I am sure, that is not load, it is not DB, it is not PHP, accualy this command:
time wget 127.0.0.1
is quite slow:
--2013-09-20 15:36:49-- http://127.0.0.1/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-09-20 15:36:52 ERROR 404: Not Found.
real 0m2.663s
user 0m0.004s
sys 0m0.004s
Response time is up to 5sec. The point of waiting is after "HTTP request sent, awaiting response..."
Page generating after this lag common for all http requests is fast, like 50ms.
I tested my web using http://tools.pingdom.com/fpt/, first response is always slow, most of content load is also slow but few are quite fast, but I cannot tell, if this tool have some sort of cache.
telnet 127.0.0.1 80
is fast, the response show without delay:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Where can be the problem? It must be something before the request goes to apache.
Please tell me at least about some debugging tools for this.
http debian-squeeze response-time lag
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02
|
show 1 more comment
I am running an apache web server on debian 6.0 with kernel 2.6.32-5-amd64.
In certain times of the day, usually when more people are online, the server have very slow responses. I am sure, that is not load, it is not DB, it is not PHP, accualy this command:
time wget 127.0.0.1
is quite slow:
--2013-09-20 15:36:49-- http://127.0.0.1/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-09-20 15:36:52 ERROR 404: Not Found.
real 0m2.663s
user 0m0.004s
sys 0m0.004s
Response time is up to 5sec. The point of waiting is after "HTTP request sent, awaiting response..."
Page generating after this lag common for all http requests is fast, like 50ms.
I tested my web using http://tools.pingdom.com/fpt/, first response is always slow, most of content load is also slow but few are quite fast, but I cannot tell, if this tool have some sort of cache.
telnet 127.0.0.1 80
is fast, the response show without delay:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Where can be the problem? It must be something before the request goes to apache.
Please tell me at least about some debugging tools for this.
http debian-squeeze response-time lag
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
I am running an apache web server on debian 6.0 with kernel 2.6.32-5-amd64.
In certain times of the day, usually when more people are online, the server have very slow responses. I am sure, that is not load, it is not DB, it is not PHP, accualy this command:
time wget 127.0.0.1
is quite slow:
--2013-09-20 15:36:49-- http://127.0.0.1/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-09-20 15:36:52 ERROR 404: Not Found.
real 0m2.663s
user 0m0.004s
sys 0m0.004s
Response time is up to 5sec. The point of waiting is after "HTTP request sent, awaiting response..."
Page generating after this lag common for all http requests is fast, like 50ms.
I tested my web using http://tools.pingdom.com/fpt/, first response is always slow, most of content load is also slow but few are quite fast, but I cannot tell, if this tool have some sort of cache.
telnet 127.0.0.1 80
is fast, the response show without delay:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Where can be the problem? It must be something before the request goes to apache.
Please tell me at least about some debugging tools for this.
http debian-squeeze response-time lag
http debian-squeeze response-time lag
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
asked Sep 20 '13 at 14:01
Maťo UrbašíkMaťo Urbašík
62
62
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02
|
show 1 more comment
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02
|
show 1 more comment
1 Answer
1
active
oldest
votes
I don't think 2.6 seconds is terribly slow for your average site that wasn't created by a team of full time engineers (See: google.com).
Your problem is probably in I/O, either network or disk or memory or etc.
You're going to have to trace through the application stack. This involved looking into your web server software (apache httpd, ngnix, etc), the php stack, the php code, and any backend storage mechanisms like File systems and MySQL that support the stack.
The delay could be caused by a slow disk, an unindexed mysql query, a bottleneck at the network, or even an optimized loop or function in the code. I don't think we will be able to help you much in this unless you can provide details about your environment and ask specific questions.
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f540490%2fslow-http-responses%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't think 2.6 seconds is terribly slow for your average site that wasn't created by a team of full time engineers (See: google.com).
Your problem is probably in I/O, either network or disk or memory or etc.
You're going to have to trace through the application stack. This involved looking into your web server software (apache httpd, ngnix, etc), the php stack, the php code, and any backend storage mechanisms like File systems and MySQL that support the stack.
The delay could be caused by a slow disk, an unindexed mysql query, a bottleneck at the network, or even an optimized loop or function in the code. I don't think we will be able to help you much in this unless you can provide details about your environment and ask specific questions.
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
add a comment |
I don't think 2.6 seconds is terribly slow for your average site that wasn't created by a team of full time engineers (See: google.com).
Your problem is probably in I/O, either network or disk or memory or etc.
You're going to have to trace through the application stack. This involved looking into your web server software (apache httpd, ngnix, etc), the php stack, the php code, and any backend storage mechanisms like File systems and MySQL that support the stack.
The delay could be caused by a slow disk, an unindexed mysql query, a bottleneck at the network, or even an optimized loop or function in the code. I don't think we will be able to help you much in this unless you can provide details about your environment and ask specific questions.
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
add a comment |
I don't think 2.6 seconds is terribly slow for your average site that wasn't created by a team of full time engineers (See: google.com).
Your problem is probably in I/O, either network or disk or memory or etc.
You're going to have to trace through the application stack. This involved looking into your web server software (apache httpd, ngnix, etc), the php stack, the php code, and any backend storage mechanisms like File systems and MySQL that support the stack.
The delay could be caused by a slow disk, an unindexed mysql query, a bottleneck at the network, or even an optimized loop or function in the code. I don't think we will be able to help you much in this unless you can provide details about your environment and ask specific questions.
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
I don't think 2.6 seconds is terribly slow for your average site that wasn't created by a team of full time engineers (See: google.com).
Your problem is probably in I/O, either network or disk or memory or etc.
You're going to have to trace through the application stack. This involved looking into your web server software (apache httpd, ngnix, etc), the php stack, the php code, and any backend storage mechanisms like File systems and MySQL that support the stack.
The delay could be caused by a slow disk, an unindexed mysql query, a bottleneck at the network, or even an optimized loop or function in the code. I don't think we will be able to help you much in this unless you can provide details about your environment and ask specific questions.
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
answered Sep 20 '13 at 15:26
Daniel WidrickDaniel Widrick
3,0622820
3,0622820
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
add a comment |
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
2.6 seconds IS terribly slow, when the content itself is generated in 50-100ms. Can you give me some tips for performance monitoring tools on IO, network, HDD and memory? MySQL is not the issue, queries are fast. I'm monitoring them.
– Maťo Urbašík
Sep 23 '13 at 7:03
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
The server behavior makes it sound like there is a bit of caching going on. SSL session caching, content caching, MySQL query caching, Linux file caching, etc... All would cause new requests to be slow and subsequent ones quite quick. Without metrics on the whole stack, we can't diagnose it in a specific manor.
– Daniel Widrick
Sep 23 '13 at 7:26
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
What can I send here, that'll be relevant to the problem? Configs, logs, dmesg, ...?
– Maťo Urbašík
Sep 23 '13 at 20:19
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
You will likely have to find someone willing to audit your entire stack. Look at the code, the server, the back ends, the network etc. There is a problem.. But right now.. It could be anywhere.
– Daniel Widrick
Sep 23 '13 at 20:22
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f540490%2fslow-http-responses%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should make a wget on an existing site. In your case you get a 404.
– René Höhle
Sep 20 '13 at 14:14
How many people you have online ?, what is your apache configuration ? maybe your max apache request is to low.
– Skamasle
Sep 20 '13 at 14:18
You really need to provide more information. What sort of page is getting loaded, how many requests per page, how many people, web server logs, top etc
– Drew Khoury
Sep 20 '13 at 14:44
404 error does not matter. When everything is OK, 404 response is fast, as should be: > --2013-09-23 08:11:15-- localhost Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-23 08:11:15 ERROR 404: Not Found. real 0m0.003s user 0m0.004s sys 0m0.000s
– Maťo Urbašík
Sep 23 '13 at 6:12
@Skamasle Cca 200 people online according to google analytics realtime. I dont think the bottleneck is PHP. As I wrote, Im sure PHP scripts is fast, it also means DB queries. First thing in my PHPs is get microtime(), last is get microtime() again and write difference out. When request took 3 seconds, PHP generating with all the quesies is like 50-100ms. I also dont think the bottle neck is Apache. I added %T/%D to the access log, but in log, even when request is slow, it is always something like 0/42904
– Maťo Urbašík
Sep 23 '13 at 7:02