On Wednesday 21 January 2004 22:20, Alex Madon wrote:
> Well the top issued was corresponding to a concurrency of 20 (so a level
> where swap is not sollicited).
> With a concurrency of 60, swap is very high
>
> Here is a "movie" of how swap is maanged (a snapshot every 5 sec)
[used sits around 110
On Wed, Jan 21, 2004 at 04:47:57PM -0700, scott.marlowe wrote:
> On Wed, 21 Jan 2004, Alex Madon wrote:
>
> > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
> > 7 root 16 0 00 0 SW1.2 0.0 0:07 0
> > kscand/Normal
> > 5 root 15
On Wed, 21 Jan 2004, Alex Madon wrote:
> One can see that at the maximum feeling of swap (74700k free swap), the
> full picture is:
>
>
> 22:51:54 up 3:58, 6 users, load average: 47.38, 18.53, 7.79
> 131 processes: 130 sleeping, 1 running, 0 zombie, 0 stopped
> CPU states: 5.3% user 3.
Could be problem be that PHP is not using connection efficiently?
Apache KeepAlive with PHP, is a dual edged sword with you holding the
blade :-)
If I am not mistaken, what happens is that a connection is kept alive
because Apache believes that other requests will come in from the client
who ma
On Wednesday 21 January 2004 14:11, Alex Madon wrote:
> Hello,
> I am testing a web application (using the DBX PHP function to call a
> Postgresql backend).
> I have 375Mb RAM on my test home box.
[10 connections is fine, 100 is not]
> I tried to change some parameters in postgresql.conf
> max_con
On Wed, 21 Jan 2004, Alex Madon wrote:
> Hello,
> I am testing a web application (using the DBX PHP function to call a
> Postgresql backend).
I'm not familiar with DBX. Is that connection pooling or what?
> I have 375Mb RAM on my test home box.
> I ran ab (apache benchmark) to test the behavio
Alex Madon wrote:
Hello,
I am testing a web application (using the DBX PHP function to call a
Postgresql backend).
I have 375Mb RAM on my test home box.
I ran ab (apache benchmark) to test the behaviour of the application
under heavy load.
When increasing the number of requests, all my memory is
