Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: one of the website takes a very long time to load |
|
Author |
|
velocity
Joined: 14 Apr 2010 Posts: 21
|
Posted: Thu 03 Jun '10 9:16 Post subject: one of the website takes a very long time to load |
|
|
I am having a website on a reverse proxy environment which is running slow.
Here are a few statistics
recorded the website loading time in the Chrome developer tools time line section and
based on what I observed
following page elements take more than 100 ms on the website
jquery checks
113 ms http://192.168.1.5:8080/eduCommons/p...achekey0517.js
244ms http://192.168.1.5:8080/eduCommons/p...achekey1443.js
247ms http://192.168.1.5:8080/eduCommons/p...chekey5402.css
like this there are some more css and page elements which have taken
100ms or 200ms in their GET request from server.
on this link
http://www.chicagostyleseo.com/2010/03/caffeine%E2%80%99s-need-for-speedhow-to-know-if-your-site-is-slow/
they mentioned what Google has defined as a slow website following
words are mentioned.
"Google has made it clear that any process that takes more than 100
milliseconds (1/10 of a second) is too long"
So that means the website is slow.
In fact I have asked a few people to access the website on internet and they too reported the same.
In a step by step way then
1) The site http://site5.abc.com was loading slowly
(Some page elements showed 411ms in Google Developer tools snapshot [URL="http://farm5.static.flickr.com/4018/4659120495_b53bf97a58_b.jpg"]here[/URL])
2) From my laptop checked http://192.168.1.5:8080/eduCommons
( got a few page elements 211 ms and one was 770 ms a snapshot for the 700 ms attached [URL="http://farm5.static.flickr.com/4042/4658588197_f4dd59b9fd_b.jpg"]here[/URL])
3) Then to check if the site is loading slow on CentOS server itself I did
ssh -L 8080:localhost:8080 root@192.168.1.5
4) Then from my laptop when above ssh connection on step 3 was alive
http://localhost:8080/eduCommons
and saw a page element loading at 411 ms.
If I am not wrong then by step 4 it is confirming that site is slow on server itself.
After reading [URL="http://prefetch.net/blog/index.php/2007/01/02/measuring-apache-request-processing-time/"]this page [/URL]
I added
Code: |
<IfDefine RequestTime>
Header set X-Request-Received: %t
Header set X-Request-Processing-Time: %D
</IfDefine>
|
I am able to see some response log. in /var/log/httpd/site-in-question-resp
Now tell me what should I post
Code: |
192.168.1.5 3062 403 5043
192.168.1.5 2826 403 5043
|
What does this tell me ?
What more should I do to check it and how can I over come this problem? |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7373 Location: Germany, Next to Hamburg
|
Posted: Fri 04 Jun '10 11:20 Post subject: |
|
|
The Header set adds a header to the browser. That is not viewable in the log file.
You have to use a tool to view the header like curl in the example or any other tool to view the header apache sends. And start apache with -DRequestTime to make that work. |
|
Back to top |
|
KenyaBreit
Joined: 02 Feb 2011 Posts: 1
|
Posted: Wed 02 Feb '11 21:52 Post subject: |
|
|
James Blond wrote: | The Header set adds a header to the browser. That is not viewable in the log file.
You have to use Noocube to view the header like curl in the example or any other tool to view the header apache sends. And start apache with -DRequestTime to make that work. |
Try modifying the header views, you should be okay with the code. |
|
Back to top |
|
|
|
|
|
|