In my case, it was a account issue. My account was the only one that was
slow. I had duplicate events on all my calendars and my query size (cf
sogo.log) was about 500k.

I juste remove my accout data with  :

sogo-tool remove user

and now everything woks well.

Thanks for your attention guys.

Le 29 mars 2012 11:14, Khapare Joshi <khapar...@gmail.com> a écrit :

> hello all,
>
> I dealt with sogo slow performance earlier - perhaps you can find in the
> list. I deployed sogo at my work around feb last year and is doing well.
> Although we have 17000+ users in our cyrus (imap server), only 6000 of
> those users are now using sogo. This might change very soon when we will
> enforce everyone to use sogo (goodbye to old sq mail).
>
> With the performance issue with the sogo. I also use imapproxy in between
> imap server and sogo server. This has certainly help to increase
> performance at least for me. Also, seach in mailing list as "Sogo Slow
> performance" - this will give you some idea how to optimize your sogo that
> we discussed. So what I did is: increase the number of PREFORK to 70(in
> /etc/sysconfig/sogo) and you need minimum 3 postgres connection per sogod
> which means:
>
> if you increase prefork to 70 then your postgres connection should be 3*70
>
> This has helped at least for me.
>
> There are probably other technique to optimize sogod but at this time this
> is good for me:) try doing this and see what happens.
>
> Khapare
>
>
>
> On Wed, Mar 28, 2012 at 9:29 AM, James James <jre...@gmail.com> wrote:
>
>> I am using Apache2 and memcached with sogo 1.3.14
>>
>> James
>>
>> Le 28 mars 2012 11:19, Martin Seener <mar...@seener.de> a écrit :
>>
>>  are u using apache2 with memcached? we have one sogo 1.3.12c with
>>> iRedMail running on the smallest JiffyBox and its quite fast.
>>>
>>> Am 3/28/12 11:12 AM, schrieb James James:
>>>
>>> Hi,
>>>
>>> I have the same problem too. It's take about five seconds to commit a
>>> change from and reload the web interface. On the demo page (
>>> http://sogo-demo.inverse.ca/SOGo/so/sogo1/Calendar/view  login:sogo1
>>> passwd: sogo1) , it's a faster.
>>>
>>> I am using RHEL6, 48Gb RAM and a local postgresql server.
>>>
>>> Can you give us some clues to tune (and improve) the performances ?
>>>
>>> Regards
>>>
>>>
>>>
>>> Le 28 mars 2012 08:45, Alessio Cecchi <ales...@skye.it> a écrit :
>>>
>>>> Il 27/03/2012 19:52, Marco Coli ha scritto:
>>>>
>>>>  Il 27/03/2012 08:57, Alessio Cecchi ha scritto:
>>>>>
>>>>>>
>>>>>> Hi Marco,
>>>>>>
>>>>>> what IMAP server are you using? Dovecot should have better performance
>>>>>> than Cyrus.
>>>>>>
>>>>>
>>>>> I am using cyrus-imapd-2.4.14-1.el6.x86_64.
>>>>> Are you sure about best Dovecot performances? For us is not possible to
>>>>> migrate, we are using Cyrus for the last 10 years.
>>>>> In the daily use, with Thunderbird as a client or with squirrelmail as
>>>>> web application, we never experienced any performance issue.
>>>>>
>>>>
>>>>  I thought it was a new installation, in your case you can not switch
>>>> to dovecot, at least not simply.
>>>>
>>>>
>>>>
>>>>>> Have you properly configured memcached?
>>>>>>
>>>>>>
>>>>> Well, it depends on what you intend with "properly". At first memcached
>>>>> was not active (as I noticed on sogo logs). After this I started it,
>>>>> with these parameters:
>>>>> PORT="11211"
>>>>> USER="nobody"
>>>>> MAXCONN="1024"
>>>>> CACHESIZE="64"
>>>>> OPTIONS=""
>>>>>
>>>>> But nothing has changed about this performance issue.
>>>>> Marco Coli
>>>>>
>>>>
>>>>  Do you have in your SOGo config:
>>>>
>>>> SOGoMemcachedHost 127.0.0.1
>>>>
>>>> Should be by default.
>>>>
>>>>
>>>> --
>>>> Alessio Cecchi is:
>>>> @ ILS -> http://www.linux.it/~alessice/
>>>> on LinkedIn -> http://www.linkedin.com/in/alessice
>>>> Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
>>>> @ PLUG -> ex-Presidente, adesso senatore a vita,
>>>> http://www.prato.linux.it
>>>> @ LOLUG -> Socio http://www.lolug.net
>>>> --
>>>> users@sogo.nu
>>>> https://inverse.ca/sogo/lists
>>>>
>>>
>>>
>>
>
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to