You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/12/09 08:07:00 UTC
[jira] [Commented] (JAMES-3467) Experimental cache for DomainList
calls
[ https://issues.apache.org/jira/browse/JAMES-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246345#comment-17246345 ]
Benoit Tellier commented on JAMES-3467:
---------------------------------------
https://github.com/linagora/james-project/pull/4115 contributes this.
> Experimental cache for DomainList calls
> ---------------------------------------
>
> Key: JAMES-3467
> URL: https://issues.apache.org/jira/browse/JAMES-3467
> Project: James Server
> Issue Type: Improvement
> Components: data
> Affects Versions: master
> Reporter: Benoit Tellier
> Priority: Major
>
> Hello there,
> Upon my load testing campaign, I noticed `SELECT * FROM domains WHERE domain=xxx;` to be one of our "hot" query, both on JMAP load when JWT is used (because there is a lookup to the domain before granting access), but also backend processing.
> This query load have a real impact (low but real) on the load we are able to handle.
> On my use case (on premise in customer site) the domains (almost) never change, and, say, 10s propagation upon creation are acceptable.
> Thus I would like to propose an opt-in cache mechanism to reduce the query load on Cassandra (but other implementation as well!). A cache on each node is ok, as the volume of domain is expected-to-be very low.
> Of course, it should be explicitly configured, and disabled by default. Of course we should warn this is experimental.
> Expected outcome is a 99% decrease of that query volume.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org