[
https://issues.apache.org/jira/browse/JAMES-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3713.
---------------------------------
Fix Version/s: 3.7.0
Resolution: Fixed
> DLP matcher: enable caching
> ---------------------------
>
> Key: JAMES-3713
> URL: https://issues.apache.org/jira/browse/JAMES-3713
> Project: James Server
> Issue Type: Improvement
> Components: data, Mailet Contributions
> Affects Versions: master
> Reporter: Benoit Tellier
> Priority: Major
> Labels: perf
> Fix For: 3.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Querying DLP rules on top of Cassandra relies on Event sourcing, involves
> reading a potentially large event stream and involves some SERIAL reads
> (LightWeight transactions) for each processed emails. Conducting flame graphs
> on Cassandra tend to show 20% of its activity consists of Paxos transactions
> for LWTs and in my setup DLP accounts for ~10% of the LWTs.
> DLP rules depending on the domain of the sender, the cardinaility is
> extremely low.
> Also, we can afford a window of inconsistencies in rules application (eg a
> minute)
> This makes caching very appealing...
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]