Which database backend are you using?

> Latelly we've been experiencing huge slowdowns on the server running OTRS.
> It only runs OTRS and nothing more, so there is no other process that may
> be using mem/disc/cpu.
>
> 15:20:35  up 20 days,  3:19,  1 user,  load average: 78.75, 101.80, 87.94
> 189 processes: 186 sleeping, 3 running, 0 zombie, 0 stopped
> CPU states:  cpu    user    nice  system    irq  softirq  iowait    idle
>            total    1.7%    0.0%   13.5%   4.9%     0.0%   79.7%    0.0%
> Mem:   384200k av,  379252k used,    4948k free,       0k shrd,    1180k
> buff
>                     280884k actv,   67428k in_d,    1292k in_c
> Swap:  915696k av,  722552k used,  193144k free                   11108k
> cached
>
> The problem is, as you can see, with the memory usage. Sorting the top
> output by mem usage, I can see that I have lots of httpd processes each
> with 20M of mem usage.
>
> Doing a ps auxww | grep httpd | wc
> I get 133 processes running.
>
> The only way to solve this problem is to restart the apache server.
> Does it has anything to do with session timeout? Anyone experimented
> similar problems ? Solutions ?
>
> Thanks in advance,
>
>  Duarte Cordeiro
>
> _______________________________________________
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
> Support oder Consulting f�r Ihr OTRS System?
>



--------------------------------------------------------
This message was sent using MetroWEB's AirMail service.
http://www.metroweb.co.za/ - full access for only R73.
Free Web Accelerator, WebMail, Calendar, Anti-Virus, 
Anti-Spam, 10 emails, 100MB personal webspace, and more!
Phone Now!  086 11 11 440
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting f�r Ihr OTRS System?
=> http://www.otrs.de/

Reply via email to