High volume of lint report events consume excessive resources and lead to performance issues about monorepo HOT 2 CLOSED

from internal

TL;DR an api change is required. The existing messageLintReports.getAll.subscribe() api is designed to produce one event on every message change, and each of those events includes all lint reports for all messages. We won't tackle that in PR 2108.

from monorepo.

and more details from this internal discord on feb 29.

I took another look and ran some experiments with throttling

bottom line - there are exactly 2000 lint report events in the test because messageLintReports.getAll.subscribe() produces an event on every message change, and each of those events includes all lint reports for all messages.

Throttling would mean changing the api not to send an event per message update, or not to send the full list of reports per event.

iow there is no throttling opportunity left which does not alter the api semantics.
Image

from monorepo.