Re: Performance problem

2018-02-05 Thread Nicolas Pinault
changes takes about 20s seconds. Pushing is very slow. Any idea of why I get this performance problem ? Can you say more about the setup? Using IIS? Configured how? Can you see where the time is spent? It might be tricky for "hg incoming" which has several round-trips. Are regular page

Re: Performance problem

2018-02-05 Thread Nicolas Pinault
. Any idea of why I get this performance problem ? Can you say more about the setup? Using IIS? Configured how? Can you see where the time is spent? It might be tricky for "hg incoming" which has several round-trips. Are regular page loads also slow? I've made some progress. I did

Re: Performance problem

2018-02-05 Thread Nicolas Pinault
. Any idea of why I get this performance problem ? Can you say more about the setup? Using IIS? Configured how? I followed the installation procedure described here : http://kallithea.readthedocs.io/en/stable/installation_win.html I updated my old database using the instructions on the same page

Re: Performance problem

2018-02-05 Thread Nicolas Pinault
s 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 o

Re: Performance problem

2018-02-05 Thread Dominik Ruf
he 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. >> P

Re: Performance problem

2018-02-05 Thread Nicolas Pinault
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 : ##

Re: Performance problem

2018-02-05 Thread Nicolas Pinault
ver 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

Re: Performance problem

2018-02-03 Thread Mads Kiilerich
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

Re: Performance problem

2018-02-03 Thread Mads Kiilerich
On 01/31/2018 01:26 PM, Nicolas Pinault wrote: 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

Re: Performance problem

2018-01-31 Thread Dominik Ruf
us 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? > >

Re: Performance problem

2018-01-31 Thread Nicolas Pinault
econds. 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 configu

Performance problem

2018-01-31 Thread Nicolas Pinault
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 ? Nicolas