If you're hosting things for internal consumption it's a generally good rule to put the memory burden on the server if you can.
And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority.
That's fair
> And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority.
Stop hosting everything on Amazon, it's a total rip-off for raw compute.
64GiB of ram shouldn't be costing you more than $50/m (for some kind of colo like Hetzner)
2GiB of ram should probably be closer to $10 for a single VM instance with someone like Tilaa or Vultr (after tax)
Meaning one you start hitting 8GiB of total consumption for all your services it's cheaper to make the leap to 64GiB of ram and go with a colo.
I guess it can make sense if you're a business. But then the question is always "why don't we just use Teams"
2gb idle is disqualifyingly high ram usage.
I'm used to running things like confluence and jira that consume as much as 140GiBs for a production.
Mattermost also uses something in the realm of 10G for anything you would consider a reasonable number of people.
This is like arguing household budgets when discussing business expenses.
Clearing $1k on the company is fine, but would be unpaletable at home.
If you can't stomach the cost then that's fine, but it is an appropriate trade-off to put the bulk of the memory burden on the server.
For reference, the last conferencing solution I ran was about 512mb at 10 users unless TURN relay was happening.
JIRA is one of the worst performing and slowest applications in the world. "Waiting for JIRA" was literally a running joke at my last job.
That some software is especially subpar is not an excuse for other software to perform a bit poorly.
