shout
shout copied to clipboard
Option to store messages in a flat-file
As all the messages are currently stored in-memory, when the number of users increases or the amount of messages increases, memory can fill up very easily resulting in a crash. It would be nice to have an option to store messages in a flat-file rather so that Shout can be used for large/active group chats.
@thisisdarshan you're right, it's definitely something we may want to do IMHO. Any figures/tests allowing to take the measure of the current issue storing everything in RAM ?
This is really hardware agnostic. But from my experience, about 100-200 users can easily fill up ec2 micro instance (with 1GB RAM) in a week time. Sometimes earlier than that.
See #391 (already merged in Shuo)
@floogulinc, it looks good but i was hoping of something that stores in json.
This is really hardware agnostic. But from my experience, about 100-200 users can easily fill up ec2 micro instance (with 1GB RAM) in a week time. Sometimes earlier than that.
@thisisdarshan Do you mean 100-200 shout users oh 100-200 buddies in the chans you're chatting on ?
I would really love this feature as well, my 512M DO server is almost full. :+1:
@JocelynDelalande 100-200 shout users, but there are only 2 active channels in the network.
@zkanda how many users ?
(/me is getting feedback for https://github.com/erming/shout-roadmap/issues/3)
@thisisdarshan, I recorded that in the roadmap: https://github.com/erming/shout-roadmap/pull/5/files#diff-04c6e90faac2675aa89e2176d2eec7d8R14 (to be merged soon).
However, there is no real benefit in storing that in JSON, which would be a flavor-of-the-day choice here. Simple flat-file would probably be best, but that goes into the pros and cons to discuss about in the roadmap. If we can go with a driver mechanism (to handle database connections as external drivers), nothing prevents someone to write a heavier solution with JSON, while keeping the defaults as the bare minimum. Makes sense? :-)
Make sense @astorije. Thank you for adding this to the road-map. Looking forward to the second phase of Shout. Do we have any plans on when can we start implementing some of the new features listed on the roadmap?
Sadly, not yet. However, the more we can discuss details in the roadmap, the easier it will be to get that to the code. Feel free to dump your ideas in issues and PRs in the roadmap so that we can get as many points of view as possible. Of course we won't be able to satisfy everyone, but it will help avoiding dead ends or bad choices!
Hi, any progress in this issue during the last 2 years? I'm really hoping for this feature as well and hopefully a method to backup the database somewhere else as well
hey @leopck : Shout's currently inactive, and I'd check out thelounge (the official fork)
that being said, Lounge doesn't have messages saving yet, but there is a WIP pull request to implement it, here: https://github.com/thelounge/lounge/pull/663