Now that's a new (and important!) piece of information. Your server
runs slow for 10 *minutes* after your script has made its request?
To me, that indicates that important data wound up getting swapped to
disk on the server, and the slow behavior reported by other users is
the result of that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2013 12:05 AM, Grant wrote:
The responses all come back successfully within a few seconds.
Can you give me a really general description of the sort of
problem that could behave like this?
Your server is just a single computer, running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2013 08:53 PM, Stroller wrote:
On 10 February 2013, at 05:05, Grant wrote:
... Your server is just a single computer, running multiple
processes. Each request from a user (be it you or someone else)
requires a certain amount of
On 11/02/2013 19:43, Michael Mol wrote:
Now that's a new (and important!) piece of information. Your server
runs slow for 10 *minutes* after your script has made its request?
To me, that indicates that important data wound up getting swapped to
disk on the server, and the slow behavior
On 11 February 2013, at 17:43, Michael Mol wrote:
...
If so, I don't understand why apache2 seems to bog down a bit for
about 10 minutes afterward.
Now that's a new (and important!) piece of information. Your server
runs slow for 10 *minutes* after your script has made its request?
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2013 06:07 PM, Stroller wrote:
On 11 February 2013, at 17:43, Michael Mol wrote:
...
If so, I don't understand why apache2 seems to bog down a bit
for about 10 minutes afterward.
Now that's a new (and important!) piece of
On Tuesday 12 February 2013 00:04:52 Michael Mol wrote:
Primarily, what bothers me is your typically acerbic tone, and that
your posts often (at least to my perception) carry more pejorative
than useful information.
I've not noticed that, for what it's worth.
--
Peter
On 12 February 2013, at 00:04, Michael Mol wrote:
I am sorry if I have caused you offence on any other occasion - if
so, please feel free to explain why.
Primarily, what bothers me is your typically acerbic tone, and that
your posts often (at least to my perception) carry more pejorative
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2013 08:05 PM, Stroller wrote:
On 12 February 2013, at 00:04, Michael Mol wrote:
I am sorry if I have caused you offence on any other occasion -
if so, please feel free to explain why.
Primarily, what bothers me is your typically
On 10 February 2013, at 05:05, Grant wrote:
...
Your server is just a single computer, running multiple processes.
Each request from a user (be it you or someone else) requires a
certain amount of resources while it's executing. If there aren't
enough resources, some of the requests will
There are several things you can do to improve the state of things.
The first and foremost is to add caching in front of the server, using
an accelerator proxy. (i.e. squid running in accelerator mode.) In
this way, you have a program which receives the user's request, checks
to see if it's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/09/2013 05:36 AM, Adam Carter wrote:
There are several things you can do to improve the state of
things. The first and foremost is to add caching in front of the
server, using an accelerator proxy. (i.e. squid running in
accelerator mode.)
Sure, so long as Apache doesn't have any additional modules loaded. If
it's got something like mod_php loaded (extraordinarily common),
mod_perl or mod_python (less common, now) then the init time of
mod_php gets added to the init time for every request handler.
Interesting, so if you have
On Feb 9, 2013 9:26 PM, Adam Carter adamcart...@gmail.com wrote:
Sure, so long as Apache doesn't have any additional modules loaded. If
it's got something like mod_php loaded (extraordinarily common),
mod_perl or mod_python (less common, now) then the init time of
mod_php gets added to the
Can't; mod_php isn't compatible with mpm_worker. You have to use a
single-threaded mpm like prefork or itk.
Anyway, you're starting to get the idea why you want a caching proxy in
front of apache.
Indeed. Thanks for your comments.
The responses all come back successfully within a few seconds.
Can you give me a really general description of the sort of problem
that could behave like this?
Your server is just a single computer, running multiple processes.
Each request from a user (be it you or someone else) requires a
A little more infromation would help. like what webserver, what kind of
requests, etc
-Kevin
It's apache and the requests/responses are XML. I know this is
pathetically little information with which to diagnose the problem.
I'm just wondering if there is a tool or method that's good to
On Fri, Feb 8, 2013 at 5:10 PM, Grant emailgr...@gmail.com wrote:
A little more infromation would help. like what webserver, what kind of
requests, etc
-Kevin
It's apache and the requests/responses are XML. I know this is
pathetically little information with which to diagnose the problem.
A little more infromation would help. like what webserver, what kind of
requests, etc
-Kevin
It's apache and the requests/responses are XML. I know this is
pathetically little information with which to diagnose the problem.
I'm just wondering if there is a tool or method that's good to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/08/2013 09:39 PM, Grant wrote:
A little more infromation would help. like what webserver,
what kind of requests, etc
-Kevin
It's apache and the requests/responses are XML. I know this is
pathetically little information with which to
A little more infromation would help. like what webserver, what kind of
requests, etc
-Kevin
On 02/06/2013 07:13 PM, Grant wrote:
I have a script that makes 6 successive HTTP requests via
LWP::UserAgent. It runs fine and takes only about 3 seconds, but
whenever it is run I start receiving
21 matches
Mail list logo
