Mercurial > evolve
comparison README @ 2366:2241433a77e5
obshashrange: warm the cache at the end of each transaction
This will help having warmed cache for read only client.
The warming is still imperfect in case of markers that trigger a reset, but we
are in a better place than what we used to be.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Fri, 12 May 2017 21:21:31 +0200 |
| parents | d8ea60fcfbc9 |
| children | a0099d568ef8 |
comparison
equal
deleted
inserted
replaced
| 2365:4b8b7fd135eb | 2366:2241433a77e5 |
|---|---|
| 117 | 117 |
| 118 - add a debugobshistory command to inspect the obs-history of a changeset | 118 - add a debugobshistory command to inspect the obs-history of a changeset |
| 119 - topic: have thg display topic name if possible, | 119 - topic: have thg display topic name if possible, |
| 120 - obscache: more efficient update in the (rare) case of a transaction adding | 120 - obscache: more efficient update in the (rare) case of a transaction adding |
| 121 markers without changesets | 121 markers without changesets |
| 122 - obshashrange-cache: update incrementally in the (common) case of a | |
| 123 transaction not affecting existing range, | |
| 124 - obshashrange-cache: keep the cache mostly warm after each transaction. | |
| 122 | 125 |
| 123 6.1.1 - in progress | 126 6.1.1 - in progress |
| 124 ------------------- | 127 ------------------- |
| 125 | 128 |
| 126 - also enable the new cache (from 6.1.0) for 'evolve.server-only', | 129 - also enable the new cache (from 6.1.0) for 'evolve.server-only', |