High cpu usage after ReadJournal instantiation
See original GitHub issueHi, when I just instantiate a ReadJournal something happen with mongo drive (reactivemongo) and cpu usage increase a lot. This is what I’m doing:
val readJournal: ScalaDslMongoReadJournal = PersistenceQuery(context.system)
.readJournalFor[ScalaDslMongoReadJournal](MongoReadJournal.Identifier)
Any advice?
Thanks for your help!
Regards, Rodrigo.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
sudden High CPU usage - Microsoft Community
I've recently started experiencing extreme cpu usage numbers when doing basic tasks. It idles at around 150-20% yet ramps up to 60-100% when ......
Read more >How to Fix High CPU Usage - Intel
Find out all the reasons why your PC displays high CPU usage. Our step-by-step guide will show you how to fix your CPU...
Read more >c# - Instantiate uses a lot of CPU resources, how to switch to ...
After some time I use gameObject.Destroy() on not needed objects. And here comes the problem: On Instantiate I see 70% CPU usage in...
Read more >High CPU usage on HA satellite after reload #7590 - GitHub
Hello, I am seeing a very high load on a HA pair of satellites in one zone after reloading Icinga or restarting the...
Read more >Troubleshoot High CPU usage by the "System" process
Introduction. High CPU usage by the "System" process can often be caused by a hardware driver issue (bug, old version, incompatility etc).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closed by #187 - released with
2.0.8
. Thanks @rodrigotn !Yes, when I disabled the realtieme persistence stop getting duplicated events.
I mean that I built my own Graph to simulate a live stream using currentByTag…