Created on 2021-02-13.23:22:00 by ced, last changed 2 weeks ago by ced.
Please open new issue.
It seems to me that the session is also present in the context. I think it should be removed also.
Also I wonder if we shouldn't extend this reasoning to technical fields present in the context:
New changeset 5c36491571e4 by Cédric Krier in branch '5.8': Remove client key from the cache's context https://hg.tryton.org/trytond/rev/5c36491571e4 New changeset fe7200d4170c by Cédric Krier in branch '5.6': Remove client key from the cache's context https://hg.tryton.org/trytond/rev/fe7200d4170c New changeset f07a73976447 by Cédric Krier in branch '5.0': Remove client key from the cache's context https://hg.tryton.org/trytond/rev/f07a73976447
New changeset 4709caabe749 by Cédric Krier in branch 'default': Remove client key from the cache's context https://hg.tryton.org/tryton-env/rev/4709caabe749
New changeset 09751b1d7f91 by Cédric Krier in branch 'default': Remove client key from the cache's context https://hg.tryton.org/trytond/rev/09751b1d7f91
Here is review331891002. I think this should be back-ported because it degrading too much the cache.
Since issue7537 which added a unique client ID to the context, the caches that depends on context are almost always missed because the
client key is unique (and so only call from the same client could hit).
status: chatting -> resolved
nosy: + nicoe
status: resolved -> chatting
messages: + msg65548
|2021-02-25 00:06:16||roundup-bot||set||messages: + msg64845|
nosy: + roundup-bot
status: testing -> resolved
nosy: + reviewbot
+ backport, review|
messages: + msg64546
status: in-progress -> testing
Showing 10 items. Show all history (warning: this could be VERY long)