-
Type: Improvement
-
Status: Open
-
Priority: Critical
-
Resolution: Unresolved
-
Affects Version/s: 7.10
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Nuxeo Drive, Performance
-
Epic Link:
-
Backlog priority:1,000
With the current algorithm, a mid-size company with 500 Drive clients and the default configuration will send 1000 requests per minute to Elasticsearch (or the database if the audit is stored there) only with calls to NuxeoDrive.GetChangeSummary operation.
This is far too much to handle for Elasticsearch where CPU and RAM will be fully consumed with a bad impact on the overall functioning of a Nuxeo application.
An optimization needs to be implemented to reduce the number of requests sent to get the changes in the audit, maybe based on a local cache of ES responses.
- is related to
-
NXP-12632 Drive: optimize audit log query
- Open
-
NXDRIVE-1054 Smart remote changes handling
- Open
-
NXP-19443 Drive: optimize ScrollDescendants operation by avoiding DocumentModel loading
- Open
-
NXP-24276 Optimize cache invalidation on drive server
- Open
-
NXP-24232 Improve getUpperBound query when storing audit in Elasticsearch
- Resolved
- mentioned in
-
Page Loading...