Performance problem

[Nicolas Pinault]

Le 05/02/2018 à 12:41, Dominik Ruf a écrit :
>
>
> On Mon, Feb 5, 2018, 12:06 Nicolas Pinault <nicolasp at aaton.com 
> <mailto:nicolasp at aaton.com>> wrote:
>
>     Le 31/01/2018 à 18:08, Dominik Ruf a écrit :
>>
>>     Can you try to use 'hg serve' on the same machine, with the same
>>     mercurial version, on the same repository and see if checking for
>>     incoming is as slow as with kallithea?
>>
>     I made the test.
>     Running 'hg serve' with the same conditions than Kallithea gives
>     the same behavior.  Checking for incoming still takes 20s.
>
> Do you use evolve?
> I had some performance problems in the past, when server and client 
> used different versions of evolve.
Yes, i use evolve.
My server hg is 4.2.3
My client hg is 4.2.2

I use TortoiseHg (Win x64) as client. I tried to upgrade it to the 
latest one (hg 4.4.2). This did not changed anything.
I tried to deactivate evolve on the client side. I got an error message 
: "obsolete feature not enabled but 3 markers found!"
However, evolve seams neither enabled nor available on the server side. 
As hg has been installed by "pip install kallithea" and evolve is not 
installed by default, this is coherent.

>
>>
>>     On Wed, Jan 31, 2018, 13:26 Nicolas Pinault <nicolasp at aaton.com
>>     <mailto:nicolasp at aaton.com>> wrote:
>>
>>         Le 31/01/2018 à 12:18, Thomas De Schampheleire a écrit :
>>>         2018-01-31 11:58 GMT+01:00 Nicolas Pinault<nicolasp at aaton.com> <mailto:nicolasp at aaton.com>:
>>>>         Hi,
>>>>
>>>>         I've changed my server. I've installed Kallithea 0.3.3 on this new server
>>>>         and migrated my repositories from 0.3.1 to 0.3.3.
>>>>         The new PC is faster than the previous one (10 years old). The new PC runs
>>>>         Windows server 2012, the old one was running Windows server 2003.
>>>>         There is no other process running on the server that notably consume
>>>>         processing power.
>>>>
>>>>         This new configuration is much slower than the previous one.
>>>>         Checking for incoming changes takes about 20s seconds.
>>>>         Pushing is very slow.
>>>>
>>>>         Any idea of why I get this performance problem ?
>>>>
>>>         Are you using the same configuration as the old server? For example,
>>>         are you (still) using Celery?
>>         I guess celery is not used since use_celery is set to false.
>>
>>         Here is my celery configuration :
>>         ####################################
>>         ###        CELERY CONFIG        ####
>>         ####################################
>>
>>         use_celery = false
>>         broker.host = serveur
>>         broker.vhost = rabbitmqhost
>>         broker.port = 5672
>>         broker.user = rabbitmq
>>         broker.password = qweqwe
>>
>>         celery.imports = kallithea.lib.celerylib.tasks
>>
>>         celery.result.backend = amqp
>>         celery.result.dburi = amqp://
>>         celery.result.serialier = json
>>
>>         #celery.send.task.error.emails = true
>>         #celery.amqp.task.result.expires = 18000
>>
>>         celeryd.concurrency = 2
>>         #celeryd.log.file = celeryd.log
>>         celeryd.log.level = DEBUG
>>         celeryd.max.tasks.per.child = 1
>>
>>
>>>         /Thomas
>>
>>         _______________________________________________
>>         kallithea-general mailing list
>>         kallithea-general at sfconservancy.org
>>         <mailto:kallithea-general at sfconservancy.org>
>>         https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>>
>
>     _______________________________________________
>     kallithea-general mailing list
>     kallithea-general at sfconservancy.org
>     <mailto:kallithea-general at sfconservancy.org>
>     https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20180205/5fdcd832/attachment.html>