9 months ago
Hello :)
I am a new user of Railway, I am quite happy with my choice. My start has been fast and smooth and I am looking forward to use with more load in the future.
I am developing a small app and have deployed a small test backend here. For persistent storage, it uses a MongoDB. Deployment was smooth and everything worked fine.
Now to the point: I am currently the only tester and the MongDB contains exactly 1 very small document (less than 1 KB I guess). That gets read something like 30-40 times a day and updated 5 times a day or so. So basically, nothing.
Still, MongoDB’s CPU usage started at around 0.2 CPU (which I find a lot already, considering there is basically no load) and is constantly increasing, now being around 0.7. Similarly, memory usage is constantly increasing, too. And finally, storage is kinda through the roof. It started at around 22 MB and went up to 216 MB now. Again, all of that for a single, super small document that is barely used.
There should be no backups or anything that I could identify as the reason for the above usages.
I deleted the MongoDB instance and volume and recreated it fully. Still, same behavior.
Could there be a misconfiguration somewhere or a Bug in the provided MongoDB image/deployment?
Thanks a lot for the help!
Tim
3 Replies
9 months ago
That's just how Mongo works in general w.r.t. resource consumption - not something we have control over unfortunately.
Status changed to Awaiting User Response Railway • 10 months ago
9 months ago
Thanks. I didn’t find a reference myself. Could you give me a hint what kind of configuration to look for?
Status changed to Awaiting Railway Response Railway • 10 months ago
9 months ago
I'm sorry but we cannot provide support or assistance with 3rd party software, besides, I'm sure that there are plenty of online articles that would prove far more helpful than us.
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Solved brody • 10 months ago