You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Tony Anecito <ad...@yahoo.com> on 2009/02/17 18:14:33 UTC
[users@httpd] Why Would Apache be so slow??
Hi All,
I am using Apache 2.4 and it is taking 10s of seconds to download small files. for example:
200 49018 5046875
The firs param is the http status the second the file size and the third the time %D or 5 seconds.
I tried a dsl speed test and I am getting 2Mbps upload which seems healthy.
I have a dual core AMD64 5200+ with SATA2 drives that are defragged. I am using Windows 2000 professional.
Any ideas? Any tools I can use to diagnose the problem? I tried using ab from the Apache bin directory but I get invalid url when I try it.
Should not Apache cache files? I have over 1GB free of fast memory.
I also setup some tuning based on a blog I found I have:
ThreadsPerChild 250
MaxRequestsPerChild 0
ProxyRequests Off
KeepAlive On
KeepAliveTimeout 15
MaxKeepAliveRequests 80
This is extreemly frustrating to see Apache so slow.
Regards,
-Tony
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Tony Anecito <ad...@yahoo.com>.
Hi Andre,
Here is another thought that might explain things. Suppose a web page has up to 10 22KB images for tabs and the browser opens up say 8 sockets and the bandwidth of the user was 1Mbps. Would the fact that many sockets were allowed by the browser saturate the user side bandwidth? Like CPU utilization the network folks might normally want to run it lower else the number of collisions might get so high the overall effect might be a large delay or load time.
I thought somewhere on the Apache site there was a recommendation to number of images to a page and the size?
Just wondering,
-Tony
--- On Tue, 2/17/09, Tony Anecito <ad...@yahoo.com> wrote:
> From: Tony Anecito <ad...@yahoo.com>
> Subject: Re: [users@httpd] Why Would Apache be so slow??
> To: users@httpd.apache.org
> Date: Tuesday, February 17, 2009, 10:10 PM
> Hi Andre,
>
> Thanks for the writeup. I have fiber instead of copper but
> I suspec the fiber is shared by putting in some type of
> optical hub perhaps.
>
> That said I had a troubleshooting session with the ISP and
> it was narrowed down to the network somewhere. He wanted me
> to bypass the router so I just went an bought another one
> since it was an old one anyway but it did not make a
> difference. I later called the company hosting my url
> godaddy and they did some tests but could not fault the DNS
> and I ran some DSL performance tests myself and the DNS
> seemed fast enough. I do have wireshark installed but have
> not tried capturing traffic to see if anything can be
> gleemed from it.
>
> Funny thing was godaddy tested the url and it did not seem
> slow to them. Which made the issue even more confusing.
>
> So I am down to the ISP's device to convert light
> signals the ethernet and dsiabling the remaining two
> comnputers on the network tonight. I will try powering down
> the light to ethernet converter after the 2 computers are
> offline to see what happens.
>
> Again many thanks and I will run those tests after I get to
> the root cause of the performance issue.
>
> -Tony
>
>
>
>
> --- On Tue, 2/17/09, André Warnier <aw...@ice-sa.com>
> wrote:
>
> > From: André Warnier <aw...@ice-sa.com>
> > Subject: Re: [users@httpd] Why Would Apache be so
> slow??
> > To: users@httpd.apache.org
> > Date: Tuesday, February 17, 2009, 4:57 PM
> > In short, what your tests are showing you is that
> Apache on
> > its own (not quite, but close enough) gives you the
> file in
> > 20 ms. The rest (the 5000 ms you measured before,
> minus 20
> > ms) is the network.
> > Score : Apache 1, network 249.
> > That should give you a pretty good indication of what
> to
> > focus on next.
> >
> > In many more words :
> >
> > First about the Apache cache : get rid of it.
> > The server-side cache will only slow down things for
> this
> > type of test. It only helps if you have many requests
> /for
> > the same file/ in a given period of time. If you have
> only
> > one, then you are just forcing the server not only to
> send
> > the response to the browser, but also to copy this
> response
> > to the cache.. You are also forcing the server to look
> in
> > the cache each time, to see if the file is there. And
> if it
> > is there, it anyway has to read it before sending it
> to the
> > browser.
> > In addition, if the cache is in memory, then you are
> also
> > using up memory that could be better used somewhere
> else.
> >
> > Note that it would be much better to do the tests
> below
> > with a non-graphical barebones test program such as
> > Apache's ab, or wget, or curl, or (my preferred
> one for
> > this) lwp-request (perl).
> > Then you could write a script which measures the time
> from
> > the client side, and which repeats the above accesses
> any
> > number of times automatically. But if you like
> typing..
> >
> > Clear the browser cache.
> > Then try with 3 files, one after the other, with the
> > browser on the same machine as Apache :
> > - one fairly small, like the 20KB file you have been
> > testing with
> > - one say 250 KB
> > - one say 1MB
> > To be fair and avoid secondary effects, make (or get)
> an
> > "index page" showing links to your 3 files,
> and to
> > measure the time right-click on each link and do a
> > "save as..". This way you are really
> measuring
> > the time it takes Apache to serve it, and not for
> example
> > the time it takes your browser to display the page, or
> image
> > or whatever.
> > Got to eliminate the secondary effects.
> >
> > I bet that the difference in time, with the browser on
> the
> > same machine as Apache, will not be very large between
> the 3
> > above.
> > I don't remember what mod_logio exactly measures,
> but
> > if it is the total time between the arrival of the
> request
> > up to the time the complete response has gone out of
> Apache,
> > then remember that
> > a) one fixed element is the time to process the
> request,
> > finding the file etc.. That's the same no matter
> how
> > big the file.
> > b) the variable element is the time to send the
> response,
> > which depends on the response size and how fast the
> line is
> > and ..how fast the client is to read and save the
> response.
> > With the server-local browser, (b) depends essentially
> on
> > the speed of your disks.
> > You may want to repeat these tests a number of times,
> to
> > also eliminate the fact that your server (apart from
> Apache)
> > also has a disk cache. So the second time you ask for
> the
> > same file is likely to be faster, independently of
> Apache.
> > So run the above 3 downloads 5-6 times each at least,
> > discard the first one, then discard the longest and
> the
> > shortest, and average the rest.
> > You may also want to make sure that there is nothing
> else
> > significant running on your server, to eliminate those
> > effects (email server ? automatic disk indexing ?
> automatic
> > updates ?). Etc.. etc...
> > Running real benchmarks is not so easy.
> >
> > Anyway, the above times are your baseline.
> > Now try again the same 3 files with a browser on
> another
> > machine of your local network.
> > The difference with the first test will give you the
> time
> > your local network is adding to the baseline.
> > Then try again, going through your Internet
> connection.
> > Then you will see how much that is adding.
> >
> > When your ISP is renting you a DSL line for 3 Mbit/s,
> you
> > have to realise that he is also renting the same to
> your 100
> > neighbours. But he is not expecting you and all your
> 100
> > neighbours, at the same time, to be using the full 3
> Mbit/s
> > each. So his line has a total capacity of say 100
> Mbit/s at
> > best (instead of 300 Mbit/s), and he figures that on
> average
> > you and the neighbours will be satisfied. If you read
> the
> > fine print, you'll probably see that somewhere it
> says
> > "/up to/ 3 Mbit/s".
> > So if your neighbours are reading this, and trying the
> same
> > thing at the same time, don't be surprised if
> several
> > tests show widely different answers.
> >
> >
> >
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache
> HTTP
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html>
> for
> > more info.
> > To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> > " from the digest:
> > users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail:
> > users-help@httpd.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Tony Anecito <ad...@yahoo.com>.
Hi Andre,
Thanks for the writeup. I have fiber instead of copper but I suspec the fiber is shared by putting in some type of optical hub perhaps.
That said I had a troubleshooting session with the ISP and it was narrowed down to the network somewhere. He wanted me to bypass the router so I just went an bought another one since it was an old one anyway but it did not make a difference. I later called the company hosting my url godaddy and they did some tests but could not fault the DNS and I ran some DSL performance tests myself and the DNS seemed fast enough. I do have wireshark installed but have not tried capturing traffic to see if anything can be gleemed from it.
Funny thing was godaddy tested the url and it did not seem slow to them. Which made the issue even more confusing.
So I am down to the ISP's device to convert light signals the ethernet and dsiabling the remaining two comnputers on the network tonight. I will try powering down the light to ethernet converter after the 2 computers are offline to see what happens.
Again many thanks and I will run those tests after I get to the root cause of the performance issue.
-Tony
--- On Tue, 2/17/09, André Warnier <aw...@ice-sa.com> wrote:
> From: André Warnier <aw...@ice-sa.com>
> Subject: Re: [users@httpd] Why Would Apache be so slow??
> To: users@httpd.apache.org
> Date: Tuesday, February 17, 2009, 4:57 PM
> In short, what your tests are showing you is that Apache on
> its own (not quite, but close enough) gives you the file in
> 20 ms. The rest (the 5000 ms you measured before, minus 20
> ms) is the network.
> Score : Apache 1, network 249.
> That should give you a pretty good indication of what to
> focus on next.
>
> In many more words :
>
> First about the Apache cache : get rid of it.
> The server-side cache will only slow down things for this
> type of test. It only helps if you have many requests /for
> the same file/ in a given period of time. If you have only
> one, then you are just forcing the server not only to send
> the response to the browser, but also to copy this response
> to the cache.. You are also forcing the server to look in
> the cache each time, to see if the file is there. And if it
> is there, it anyway has to read it before sending it to the
> browser.
> In addition, if the cache is in memory, then you are also
> using up memory that could be better used somewhere else.
>
> Note that it would be much better to do the tests below
> with a non-graphical barebones test program such as
> Apache's ab, or wget, or curl, or (my preferred one for
> this) lwp-request (perl).
> Then you could write a script which measures the time from
> the client side, and which repeats the above accesses any
> number of times automatically. But if you like typing..
>
> Clear the browser cache.
> Then try with 3 files, one after the other, with the
> browser on the same machine as Apache :
> - one fairly small, like the 20KB file you have been
> testing with
> - one say 250 KB
> - one say 1MB
> To be fair and avoid secondary effects, make (or get) an
> "index page" showing links to your 3 files, and to
> measure the time right-click on each link and do a
> "save as..". This way you are really measuring
> the time it takes Apache to serve it, and not for example
> the time it takes your browser to display the page, or image
> or whatever.
> Got to eliminate the secondary effects.
>
> I bet that the difference in time, with the browser on the
> same machine as Apache, will not be very large between the 3
> above.
> I don't remember what mod_logio exactly measures, but
> if it is the total time between the arrival of the request
> up to the time the complete response has gone out of Apache,
> then remember that
> a) one fixed element is the time to process the request,
> finding the file etc.. That's the same no matter how
> big the file.
> b) the variable element is the time to send the response,
> which depends on the response size and how fast the line is
> and ..how fast the client is to read and save the response.
> With the server-local browser, (b) depends essentially on
> the speed of your disks.
> You may want to repeat these tests a number of times, to
> also eliminate the fact that your server (apart from Apache)
> also has a disk cache. So the second time you ask for the
> same file is likely to be faster, independently of Apache.
> So run the above 3 downloads 5-6 times each at least,
> discard the first one, then discard the longest and the
> shortest, and average the rest.
> You may also want to make sure that there is nothing else
> significant running on your server, to eliminate those
> effects (email server ? automatic disk indexing ? automatic
> updates ?). Etc.. etc...
> Running real benchmarks is not so easy.
>
> Anyway, the above times are your baseline.
> Now try again the same 3 files with a browser on another
> machine of your local network.
> The difference with the first test will give you the time
> your local network is adding to the baseline.
> Then try again, going through your Internet connection.
> Then you will see how much that is adding.
>
> When your ISP is renting you a DSL line for 3 Mbit/s, you
> have to realise that he is also renting the same to your 100
> neighbours. But he is not expecting you and all your 100
> neighbours, at the same time, to be using the full 3 Mbit/s
> each. So his line has a total capacity of say 100 Mbit/s at
> best (instead of 300 Mbit/s), and he figures that on average
> you and the neighbours will be satisfied. If you read the
> fine print, you'll probably see that somewhere it says
> "/up to/ 3 Mbit/s".
> So if your neighbours are reading this, and trying the same
> thing at the same time, don't be surprised if several
> tests show widely different answers.
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by André Warnier <aw...@ice-sa.com>.
In short, what your tests are showing you is that Apache on its own (not
quite, but close enough) gives you the file in 20 ms. The rest (the 5000
ms you measured before, minus 20 ms) is the network.
Score : Apache 1, network 249.
That should give you a pretty good indication of what to focus on next.
In many more words :
First about the Apache cache : get rid of it.
The server-side cache will only slow down things for this type of test.
It only helps if you have many requests /for the same file/ in a given
period of time. If you have only one, then you are just forcing the
server not only to send the response to the browser, but also to copy
this response to the cache.. You are also forcing the server to look in
the cache each time, to see if the file is there. And if it is there,
it anyway has to read it before sending it to the browser.
In addition, if the cache is in memory, then you are also using up
memory that could be better used somewhere else.
Note that it would be much better to do the tests below with a
non-graphical barebones test program such as Apache's ab, or wget, or
curl, or (my preferred one for this) lwp-request (perl).
Then you could write a script which measures the time from the client
side, and which repeats the above accesses any number of times
automatically. But if you like typing..
Clear the browser cache.
Then try with 3 files, one after the other, with the browser on the same
machine as Apache :
- one fairly small, like the 20KB file you have been testing with
- one say 250 KB
- one say 1MB
To be fair and avoid secondary effects, make (or get) an "index page"
showing links to your 3 files, and to measure the time right-click on
each link and do a "save as..". This way you are really measuring the
time it takes Apache to serve it, and not for example the time it takes
your browser to display the page, or image or whatever.
Got to eliminate the secondary effects.
I bet that the difference in time, with the browser on the same machine
as Apache, will not be very large between the 3 above.
I don't remember what mod_logio exactly measures, but if it is the total
time between the arrival of the request up to the time the complete
response has gone out of Apache, then remember that
a) one fixed element is the time to process the request, finding the
file etc.. That's the same no matter how big the file.
b) the variable element is the time to send the response, which depends
on the response size and how fast the line is and ..how fast the client
is to read and save the response.
With the server-local browser, (b) depends essentially on the speed of
your disks.
You may want to repeat these tests a number of times, to also eliminate
the fact that your server (apart from Apache) also has a disk cache. So
the second time you ask for the same file is likely to be faster,
independently of Apache.
So run the above 3 downloads 5-6 times each at least, discard the first
one, then discard the longest and the shortest, and average the rest.
You may also want to make sure that there is nothing else significant
running on your server, to eliminate those effects (email server ?
automatic disk indexing ? automatic updates ?). Etc.. etc...
Running real benchmarks is not so easy.
Anyway, the above times are your baseline.
Now try again the same 3 files with a browser on another machine of your
local network.
The difference with the first test will give you the time your local
network is adding to the baseline.
Then try again, going through your Internet connection.
Then you will see how much that is adding.
When your ISP is renting you a DSL line for 3 Mbit/s, you have to
realise that he is also renting the same to your 100 neighbours. But he
is not expecting you and all your 100 neighbours, at the same time, to
be using the full 3 Mbit/s each. So his line has a total capacity of
say 100 Mbit/s at best (instead of 300 Mbit/s), and he figures that on
average you and the neighbours will be satisfied. If you read the fine
print, you'll probably see that somewhere it says "/up to/ 3 Mbit/s".
So if your neighbours are reading this, and trying the same thing at the
same time, don't be surprised if several tests show widely different
answers.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Tony Anecito <ad...@yahoo.com>.
Thanks for the advice. I did make a change to the modules section but like you said I suspect the problem is outside of Apache.
My network setup uses a DLINK 1Gbps gaming router connected to the ISP wire to fiber converter then from there to the internet somehow. On the other side of my router I use 1Gbps cable connecting to 1Gbps lan cards.
I tried tests where I used a computer (Laptop) on my local network (which goes through indicates the request comes through my router and after clearing the cache reloaded the site and in my logs:
200 22834 234375
so 23KB took .234 seconds or 780Kbps which seems slow but then for my configuration not sure if this is slow but much better than what I see in my logs for requests coming through the ISP router and through the internet.
If I try from the browser on the machine that is hosting the Apache server/site then it is extreemly fast. I get typically 15-32msec for a 22K file with a http status of 200 not 304.
I called my ISP and they said try a dsl speed test which went up to 2Mbps upload but not sure if that is a true test of uploading html files through the system.
I will keep trying to understand and do some tests outside my network to see what happens.
Many Thanks,
-Tony
--- On Tue, 2/17/09, André Warnier <aw...@ice-sa.com> wrote:
> From: André Warnier <aw...@ice-sa.com>
> Subject: Re: [users@httpd] Why Would Apache be so slow??
> To: users@httpd.apache.org
> Date: Tuesday, February 17, 2009, 12:46 PM
> Tony Anecito wrote:
> > Hi All,
> >
> > I am using Apache 2.4 and it is taking 10s of seconds
> to download small files. for example:
> >
> > 200 49018 5046875
> >
> [...]
> >
> > This is extreemly frustrating to see Apache so slow.
> >
> Hi.
> It is also quite frustrating to see someone jumping to
> conclusions like that, when on the other hand Apache powers
> about 75% of public websites worldwide, and when Apache by
> itself is probably capable of serving 1000 requests like the
> above, per second.
>
> It is possible that something is definitely wrong in your
> configuration, such as the last 2 lines of your
> "Loadmodule" series:
> LoadModule logio_module modules/mod_logio.so
> LoadModule logio_module modules/mod_mem_cache.so
> (spot it ?)
>
> but it is about 100 times more likely that your problem is
> somewhere outside of Apache (such as some network problem).
> Can you describe your setup a bit more in detail ?
> Such as :
> - where is your Apache server ?
> - where is the browser you are testing with ?
> - is there something in-between ?
> - which exact URL are you trying in the browser, to get
> that file ?
> - what else is using the same "line" between your
> browser and the server ?
>
>
> Basically, if Apache tells you that it took 5 seconds to
> send a 50K file to your client, it means that it could not
> send more than 10 Kbytes/second, or roughly 100 Kbit/s.
> Since on the other hand you mention pretty fast disks
> (which can probably read more than 50 MB/second), and a line
> which can reach 2 Mbit/second, there are some 1,900
> Kbit/second getting lost somewhere.
> And it is probably not inside of Apache.
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by André Warnier <aw...@ice-sa.com>.
Tony Anecito wrote:
> Hi All,
>
> I am using Apache 2.4 and it is taking 10s of seconds to download small files. for example:
>
> 200 49018 5046875
>
[...]
>
> This is extreemly frustrating to see Apache so slow.
>
Hi.
It is also quite frustrating to see someone jumping to conclusions like
that, when on the other hand Apache powers about 75% of public websites
worldwide, and when Apache by itself is probably capable of serving 1000
requests like the above, per second.
It is possible that something is definitely wrong in your configuration,
such as the last 2 lines of your "Loadmodule" series:
LoadModule logio_module modules/mod_logio.so
LoadModule logio_module modules/mod_mem_cache.so
(spot it ?)
but it is about 100 times more likely that your problem is somewhere
outside of Apache (such as some network problem).
Can you describe your setup a bit more in detail ?
Such as :
- where is your Apache server ?
- where is the browser you are testing with ?
- is there something in-between ?
- which exact URL are you trying in the browser, to get that file ?
- what else is using the same "line" between your browser and the server ?
Basically, if Apache tells you that it took 5 seconds to send a 50K file
to your client, it means that it could not send more than 10
Kbytes/second, or roughly 100 Kbit/s.
Since on the other hand you mention pretty fast disks (which can
probably read more than 50 MB/second), and a line which can reach 2
Mbit/second, there are some 1,900 Kbit/second getting lost somewhere.
And it is probably not inside of Apache.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Glen Barber <gl...@gmail.com>.
On Tue, Feb 17, 2009 at 12:14 PM, Tony Anecito <ad...@yahoo.com> wrote:
> Any ideas? Any tools I can use to diagnose the problem? I tried using ab from the Apache bin directory but I get invalid url when I try it.
There is a tool called 'apachetop', but I don't know if it is
available for Win32.
--
Glen Barber
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Tony Anecito <ad...@yahoo.com>.
Okay. I enabled loading of what I hope are the right modules and added if statements for mem cache.
Hopefully this solves the problem.
My conf file section I changes now is:
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
LoadModule expires_module modules/mod_expires.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
LoadModule logio_module modules/mod_logio.so
LoadModule logio_module modules/mod_mem_cache.so
ProxyRequests Off
KeepAlive On
KeepAliveTimeout 15
MaxKeepAliveRequests 80
#StartServers 5
#MinSpareServers 5
#MaxSpareServers 10
#ServerLimit 15
#MaxClients 15
#MaxRequestsPerChild 2000
<IfModule mod_cache.c>
<IfModule mod_mem_cache.c>
CacheEnable mem /
MCacheSize 4096
MCacheMaxObjectCount 100
MCacheMinObjectSize 1
MCacheMaxObjectSize 2048
</IfModule>
</IfModule>
--- On Tue, 2/17/09, Tony Anecito <ad...@yahoo.com> wrote:
> From: Tony Anecito <ad...@yahoo.com>
> Subject: Re: [users@httpd] Why Would Apache be so slow??
> To: users@httpd.apache.org
> Date: Tuesday, February 17, 2009, 10:38 AM
> Hi All,
>
> Here is my module setup hopefully it will point out
> something I am missing.
>
> LoadModule actions_module modules/mod_actions.so
> LoadModule alias_module modules/mod_alias.so
> LoadModule asis_module modules/mod_asis.so
> LoadModule auth_basic_module modules/mod_auth_basic.so
> #LoadModule auth_digest_module modules/mod_auth_digest.so
> #LoadModule authn_anon_module modules/mod_authn_anon.so
> #LoadModule authn_dbm_module modules/mod_authn_dbm.so
> LoadModule authn_default_module
> modules/mod_authn_default.so
> LoadModule authn_file_module modules/mod_authn_file.so
> #LoadModule authz_dbm_module modules/mod_authz_dbm.so
> LoadModule authz_default_module
> modules/mod_authz_default.so
> LoadModule authz_groupfile_module
> modules/mod_authz_groupfile.so
> LoadModule authz_host_module modules/mod_authz_host.so
> LoadModule authz_user_module modules/mod_authz_user.so
> LoadModule autoindex_module modules/mod_autoindex.so
> #LoadModule cern_meta_module modules/mod_cern_meta.so
> LoadModule cgi_module modules/mod_cgi.so
> #LoadModule dav_module modules/mod_dav.so
> #LoadModule dav_fs_module modules/mod_dav_fs.so
> #LoadModule deflate_module modules/mod_deflate.so
> LoadModule dir_module modules/mod_dir.so
> LoadModule env_module modules/mod_env.so
> #LoadModule expires_module modules/mod_expires.so
> #LoadModule file_cache_module modules/mod_file_cache.so
> #LoadModule headers_module modules/mod_headers.so
> LoadModule imagemap_module modules/mod_imagemap.so
> LoadModule include_module modules/mod_include.so
> #LoadModule info_module modules/mod_info.so
> LoadModule isapi_module modules/mod_isapi.so
> LoadModule log_config_module modules/mod_log_config.so
> LoadModule mime_module modules/mod_mime.so
> #LoadModule mime_magic_module modules/mod_mime_magic.so
> LoadModule proxy_module modules/mod_proxy.so
> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
> #LoadModule proxy_balancer_module
> modules/mod_proxy_balancer.so
> #LoadModule proxy_connect_module
> modules/mod_proxy_connect.so
> #LoadModule proxy_http_module modules/mod_proxy_http.so
> #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
> LoadModule negotiation_module modules/mod_negotiation.so
> #LoadModule rewrite_module modules/mod_rewrite.so
> LoadModule setenvif_module modules/mod_setenvif.so
> #LoadModule speling_module modules/mod_speling.so
> #LoadModule status_module modules/mod_status.so
> #LoadModule unique_id_module modules/mod_unique_id.so
> LoadModule userdir_module modules/mod_userdir.so
> #LoadModule usertrack_module modules/mod_usertrack.so
> #LoadModule vhost_alias_module modules/mod_vhost_alias.so
> #LoadModule ssl_module modules/mod_ssl.so
> LoadModule logio_module modules/mod_logio.so
>
> --- On Tue, 2/17/09, Tony Anecito
> <ad...@yahoo.com> wrote:
>
> > From: Tony Anecito <ad...@yahoo.com>
> > Subject: [users@httpd] Why Would Apache be so slow??
> > To: "Apache Mailing List"
> <us...@httpd.apache.org>
> > Date: Tuesday, February 17, 2009, 10:14 AM
> > Hi All,
> >
> > I am using Apache 2.4 and it is taking 10s of seconds
> to
> > download small files. for example:
> >
> > 200 49018 5046875
> >
> > The firs param is the http status the second the file
> size
> > and the third the time %D or 5 seconds.
> >
> > I tried a dsl speed test and I am getting 2Mbps upload
> > which seems healthy.
> > I have a dual core AMD64 5200+ with SATA2 drives that
> are
> > defragged. I am using Windows 2000 professional.
> >
> > Any ideas? Any tools I can use to diagnose the
> problem? I
> > tried using ab from the Apache bin directory but I get
> > invalid url when I try it.
> >
> > Should not Apache cache files? I have over 1GB free of
> fast
> > memory.
> >
> > I also setup some tuning based on a blog I found I
> have:
> >
> > ThreadsPerChild 250
> > MaxRequestsPerChild 0
> >
> > ProxyRequests Off
> >
> > KeepAlive On
> > KeepAliveTimeout 15
> > MaxKeepAliveRequests 80
> >
> >
> > This is extreemly frustrating to see Apache so slow.
> >
> > Regards,
> > -Tony
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache
> HTTP
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html>
> for
> > more info.
> > To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> > " from the digest:
> > users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail:
> > users-help@httpd.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Why Would Apache be so slow??
Posted by Tony Anecito <ad...@yahoo.com>.
Hi All,
Here is my module setup hopefully it will point out something I am missing.
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
LoadModule logio_module modules/mod_logio.so
--- On Tue, 2/17/09, Tony Anecito <ad...@yahoo.com> wrote:
> From: Tony Anecito <ad...@yahoo.com>
> Subject: [users@httpd] Why Would Apache be so slow??
> To: "Apache Mailing List" <us...@httpd.apache.org>
> Date: Tuesday, February 17, 2009, 10:14 AM
> Hi All,
>
> I am using Apache 2.4 and it is taking 10s of seconds to
> download small files. for example:
>
> 200 49018 5046875
>
> The firs param is the http status the second the file size
> and the third the time %D or 5 seconds.
>
> I tried a dsl speed test and I am getting 2Mbps upload
> which seems healthy.
> I have a dual core AMD64 5200+ with SATA2 drives that are
> defragged. I am using Windows 2000 professional.
>
> Any ideas? Any tools I can use to diagnose the problem? I
> tried using ab from the Apache bin directory but I get
> invalid url when I try it.
>
> Should not Apache cache files? I have over 1GB free of fast
> memory.
>
> I also setup some tuning based on a blog I found I have:
>
> ThreadsPerChild 250
> MaxRequestsPerChild 0
>
> ProxyRequests Off
>
> KeepAlive On
> KeepAliveTimeout 15
> MaxKeepAliveRequests 80
>
>
> This is extreemly frustrating to see Apache so slow.
>
> Regards,
> -Tony
>
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org