You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.
Im running my mosca node js server on a raspberry pi zero, so resources are limited. I noticed using top that mongodb always use about 20% CPU, even when there is no messages sent over MQTT. When I run mongotop, I see that its the pubsubcollection that always has about 25ms of read activity.
Is there anyway to avoid the constant load on the pubsubcollection in mongodb?
it will be better to have a way to inject an existing mongo Connection
as we have in attachHttpServer()
so if we can make something like attachMongoConnection()
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Im running my mosca node js server on a raspberry pi zero, so resources are limited. I noticed using top that mongodb always use about 20% CPU, even when there is no messages sent over MQTT. When I run mongotop, I see that its the pubsubcollection that always has about 25ms of read activity.
Is there anyway to avoid the constant load on the pubsubcollection in mongodb?
Here are my settings:
The text was updated successfully, but these errors were encountered: