General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Large deployments


Chronological Thread 
  • From: Albert Shih < >
  • To:
  • Subject: Re: [SOGo] Large deployments
  • Date: Fri, 20 Dec 2013 11:41:26 +0100

Le 18/12/2013 à 16:28:11+0100, Jan-Frode Myklebust a écrit
> On Wed, Dec 18, 2013 at 03:55:22PM +0100, Albert Shih wrote:
> > >
> > > We at the Universität Konstanz in Germany have more than 16000 users.
> > >
> > Can you describe your infrastructure ? How many server ? (hardware &
> > Virtual), what size (Ram, CPU) ?
>
> We have around 30.000 unique users daily.
>
> The sogo-servers are 5 virtual machines with 4 cpus and 8 GB
> memory each. Top output from one of these right now:
>
> top - 16:17:22 up 15 days, 15:54, 1 user, load average: 0.16, 0.09, 0.03
> Tasks: 277 total, 2 running, 275 sleeping, 0 stopped, 0 zombie
> Cpu0 : 2.0%us, 0.7%sy, 0.0%ni, 97.0%id, 0.3%wa, 0.0%hi, 0.0%si,
> 0.0%st
> Cpu1 : 1.7%us, 0.3%sy, 0.0%ni, 98.0%id, 0.0%wa, 0.0%hi, 0.0%si,
> 0.0%st
> Cpu2 : 3.7%us, 1.0%sy, 0.0%ni, 94.6%id, 0.0%wa, 0.0%hi, 0.7%si,
> 0.0%st
> Cpu3 : 0.3%us, 0.7%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.3%si,
> 0.0%st
> Mem: 8059428k total, 5849244k used, 2210184k free, 540264k buffers
> Swap: 2097144k total, 26476k used, 2070668k free, 2298216k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
>
> 6580 root 20 0 273m 115m 3844 S 0.0 1.5 36:49.53 splunkd
>
>
> 7997 sogo 20 0 381m 62m 8796 S 0.0 0.8 0:44.65 sogod
>
>
> 6438 sogo 20 0 380m 60m 8108 S 0.0 0.8 0:55.09 sogod
>
>
> 2730 sogo 20 0 379m 59m 8708 S 0.0 0.8 0:42.99 sogod
>
>
> 6035 sogo 20 0 378m 59m 8568 S 0.0 0.8 0:44.89 sogod
>
>
> 6459 sogo 20 0 379m 59m 8164 S 0.0 0.8 0:51.07 sogod
>
>
> 17130 sogo 20 0 378m 59m 8672 S 0.0 0.8 0:46.98 sogod
>
>
> 13702 sogo 20 0 379m 58m 8600 S 0.0 0.7 0:43.08 sogod
>
>
> 6428 sogo 20 0 380m 58m 8356 S 0.0 0.7 0:51.75 sogod
>
>
> 25734 sogo 20 0 376m 57m 8896 S 0.0 0.7 0:42.47 sogod
>
>
> 8076 sogo 20 0 375m 56m 8616 S 0.0 0.7 0:38.01 sogod
>
>
> 2725 sogo 20 0 375m 56m 8336 S 2.7 0.7 0:35.36 sogod
>
>
> 2690 sogo 20 0 372m 55m 8388 S 0.0 0.7 0:38.71 sogod
>
>
> 14427 sogo 20 0 374m 55m 8620 S 0.0 0.7 0:36.37 sogod
>
>
> 8090 sogo 20 0 374m 55m 8552 S 0.0 0.7 0:36.86 sogod
>
>
> 23322 sogo 20 0 375m 54m 8244 S 0.0 0.7 0:28.58 sogod
>
>
> 13543 sogo 20 0 373m 54m 8448 S 0.0 0.7 0:25.63 sogod
>
>
> 9580 sogo 20 0 372m 54m 8584 S 0.0 0.7 0:34.44 sogod
>
>
> 28024 sogo 20 0 372m 53m 8780 S 0.0 0.7 0:33.48 sogod
>
>
> 7722 sogo 20 0 374m 53m 8640 S 0.0 0.7 0:35.03 sogod
>
>
> 8991 sogo 20 0 373m 52m 8272 S 0.0 0.7 0:23.42 sogod
>
>
> 8411 sogo 20 0 369m 50m 8496 S 0.0 0.6 0:34.35 sogod
>
>
> 6863 sogo 20 0 369m 50m 8016 S 0.0 0.6 0:32.21 sogod
>
>
> 5485 sogo 20 0 369m 50m 8668 S 0.0 0.6 0:34.20 sogod
>
>
> <snip>
>
> We kill sogod's that has been running for more than 15 cpuminutes, as
> these are normally stuck in something. I believe your sogod's must
> be stuck..

Well I try this, actually only manually, for example I just kill some sogod
process who eat ~150:00:00 time (since yesterday) and that make sogo crash
(no more connection on the web-gui, need a service sogod restart).

How you manage the kill ?

Can I ask what linux you using ?

Regards.

JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp:

Heure local/Local time:
ven 20 déc 2013 11:38:26 CET



Archive powered by MHonArc 2.6.18.

Top of page