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
Rocket.Chat can be resourcehungry due to its choice of MongoDB, which should be run in a cluster. It's the first suggestion on the Sandstorm website.
Nothing against Rocket.Chat but it seems if something like Sandstorm is going to need to take off it's going to need lightweight apps that are good at scaling down.
The text was updated successfully, but these errors were encountered:
Sandstorm's tools for Meteor apps automatically configure Mongo to run in a mode where it reasonably efficient for the Sandstorm use case. Under Sandstorm there is no reason to run Mongo as a cluster, since the idea is that you scale by creating more instances of Rocket.Chat (e.g. for separate chat rooms) rather than try to scale up one instance. Several of the top apps on Sandstorm (e.g. Wekan) are Meteor apps that use Mongo, but we haven't seen any problem with this.
Rocket.Chat on Sandstorm does have one performance problem currently in that it's very slow to start, but that's not because of Mongo but rather some sort of startup processing Rocket.Chat does, which ought to be optimized better. We might be able to solve this directly in Sandstorm eventually by using snappy-start.
Rocket.Chat can be resource hungry due to its choice of MongoDB, which should be run in a cluster. It's the first suggestion on the Sandstorm website.
Nothing against Rocket.Chat but it seems if something like Sandstorm is going to need to take off it's going to need lightweight apps that are good at scaling down.
The text was updated successfully, but these errors were encountered: