Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ayush NayyarAyush NayyarReporter
Abhishek JindalAbhishek JindalIs this a Regression?
UnknownTriage
UntriagedStory Points
1Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Ayush Nayyar
Ayush NayyarReporter
Abhishek Jindal
Abhishek JindalIs this a Regression?
Unknown
Triage
Untriaged
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created October 28, 2022 at 10:44 AM
Updated November 21, 2022 at 9:13 AM
Resolved November 1, 2022 at 3:02 AM
With the V8 upgraded to v10.7.21 , am empty js-evaluator worker (no code loaded and no traffic) takes up around 1.54 MB heap memory.
XDCR CCR for some reason has chosen to set the heap quota as 1.50 MB. Heap Quota dictates how frequently should the js-evaluator's GC run to contain it's memory usage.
However, keeping the heap quota to as low as 1.5 MB is a misconfiguration which causes GC to be triggered unnecessarily on an empty js-evaluator worker. These uneccesary GC runs might eat up precious CPU resources and may impact XDCR's performance.
Solution:
1. Either increase the heap quota to a respectable limit such as 150 MB (an empty jsevaluator's worker will never hit 150 MB).
2. Another option, which the XDCR team is best equipped to make a decision on, is to set number of js-evaluator's workers to 0. No workers, means no V8 isolates, no heap, no GC.