I’m not sure if this has been discussed before, but.
When a user logs into RT, two MySQL processes are created. When a user
does a task (i.e. goes to a specific ticket), another process is
created.
After the user logouts, these processes are still present, just in
‘sleep’ state.
This process repeats itself each time a user logs in, causing many MySQL
processes (though in sleep state).
Anyone else see this, or am I doing something wrong. We’ve seen this
(from what I can remember) back in 2.0.4, and see the sam behavior in
2.0.8pre2.
The machine running RT is running:
MySQL Client 3.23.42
FreeBSD 4.3
Apache 1.3.12
The MySQL machine is running:
MySQL Server 3.23.42
FreeBSD 4.3
darrin walton, darrinw@nixc.net
senior vice president, internet operations and engineering.
I suspect that’s Apache::DBI working its connection reuse magic for you. If you
crank down the max # of apache children, the max # of connections opened
should drop.On Fri, Sep 28, 2001 at 02:13:53AM +0000, Darrin Walton wrote:
I’m not sure if this has been discussed before, but.
When a user logs into RT, two MySQL processes are created. When a user
does a task (i.e. goes to a specific ticket), another process is
created.
After the user logouts, these processes are still present, just in
‘sleep’ state.
This process repeats itself each time a user logs in, causing many MySQL
processes (though in sleep state).
Anyone else see this, or am I doing something wrong. We’ve seen this
(from what I can remember) back in 2.0.4, and see the sam behavior in
2.0.8pre2.
The machine running RT is running:
MySQL Client 3.23.42
FreeBSD 4.3
Apache 1.3.12
The MySQL machine is running:
MySQL Server 3.23.42
FreeBSD 4.3
–
darrin walton, darrinw@nixc.net
senior vice president, internet operations and engineering.
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.