Current caching

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

Re: Performance problem

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

Re: Performance problem

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

Performance problem

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