Current caching

[Dominik Ruf]

Hi all,

I'm currently looking at the caching Kallithea does. And I'm a
bit...baffled.
The way I understand it is that first an entry is made to CacheInvalidation
to mark a cache invalid,
and later that entry is checked to decide if that cache should be
invalidated.
But why this detour? Why not invalidate the cache directly?
Can somebody explain to me why the invalidation is done via the
CacheInvalidation table?

cheers
Dominik
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
https://lists.sfconservancy.org/mailman/listinfo/kallithea-general

Re: Performance problem

[Dominik Ruf]

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?

On Wed, Jan 31, 2018, 13:26 Nicolas Pinault  wrote:

> Le 31/01/2018 à 12:18, Thomas De Schampheleire a écrit :
>
> 2018-01-31 11:58 GMT+01:00 Nicolas Pinault  
> :
>
> 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@sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
https://lists.sfconservancy.org/mailman/listinfo/kallithea-general

Re: Performance problem

[Nicolas Pinault]

Le 31/01/2018 à 12:18, Thomas De Schampheleire a écrit :

2018-01-31 11:58 GMT+01:00 Nicolas Pinault :

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@sfconservancy.org
https://lists.sfconservancy.org/mailman/listinfo/kallithea-general

Performance problem

[Nicolas Pinault]

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 ?

Nicolas
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
https://lists.sfconservancy.org/mailman/listinfo/kallithea-general