Done
Details
Assignee
Kateryna SenchenkoKateryna SenchenkoReporter
Kateryna SenchenkoKateryna SenchenkoPriority
P2Story Points
8Sprint
NoneDevelopment Team
FolijetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Kateryna Senchenko
Kateryna SenchenkoReporter
Kateryna Senchenko
Kateryna SenchenkoPriority
Story Points
8
Sprint
None
Development Team
Folijet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 12, 2020 at 11:05 AM
Updated March 18, 2020 at 8:18 AM
Resolved February 24, 2020 at 10:47 AM
The probable cause of performance issues in pub-sub lies in running out of memory by putting too much on the write queue of KafkaProducer. To fix the issue try the following:
Upon receiving an event - respond before sending event to kafka
Remove redundant querying of the db for getting messaging modules by caching
Replace single shared KafkaProducer with other option KafkaProducer
Add logging to pub-sub