server estimation( cpu,ram,bandwitch,ssd)
-
@humptydumpty please delete your comment. you did not give any answer pertaining to the question. the question is precise.. nothing to do with fresh install
-
@blaise said in server estimation( cpu,ram,bandwitch,ssd):
please delete your comment
While his answer may not have been helpful to you, there is no reason to be rude.
The official documentation gives the following numbers for scaling: https://docs.rocket.chat/installation/hardware-requirements
-
@blaise Not a great start to your membership here in the forum. The response may not have answered your question exactly but that hardly justifies your impolite reaction.
Incidentally, a simple Google search would have found you this:
https://docs.rocket.chat/installation/hardware-requirements
A bit of multiplication and you should have a reasonable idea what you are likely to need.
Edit: I see @fbartels was a bit quicker.
-
@blaise I only posted the fresh install info because I never found that info posted anywhere so it'll come in handy for those of us looking to run Rocket chat for a small team/family. The recommended specs are 2GB RAM but it seems it'll be able to run on lower. Also, I was going to offer to use my install for testing but not with that attitude.
-
@blaise said in server estimation( cpu,ram,bandwitch,ssd):
@humptydumpty please delete your comment. you did not give any answer pertaining to the question. the question is precise.. nothing to do with fresh install
That's kind of a rude reply and I think he did give very pertinent answer as as least it gives a very good point to start from.
Next time, please be kind and, I mean, asking to remove a posted comment is certainly not of yours to decide lol
Andy -
@humptydumpty oo I am sorry. i just have a heavy day...
-
@blaise It heavily depends on the usage. 1.000 members without any interaction? 200 concurrent uses?
Good news is: you can easily restore your whole Cloudron or a single app on a "bigger" instance. (just in case your vps provider can't do an upgrade of your vps).
So the advice is: start with a smaller instance and throw some more cpu&ram on it in a later state with knowledge about the load.