Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Approx platform size and RAM consumption #54

Closed
craxed opened this issue Jul 2, 2021 · 7 comments
Closed

Suggestion: Approx platform size and RAM consumption #54

craxed opened this issue Jul 2, 2021 · 7 comments

Comments

@craxed
Copy link

craxed commented Jul 2, 2021

Adding approx platform size and RAM consumption in each article under "Build your own platform!".
Each platform have its own RAM usage and disk usage. For limited size servers, this would be helpful.

@LukeSmithxyz
Copy link
Owner

A good idea. People who host the listed services frequently should feel free to volunteer their footprints. For some things, I'm sure it varies a lot too.

@ghost
Copy link

ghost commented Jul 2, 2021

I guess we could collect here, then figure out how to format and add it to articles.
Gitea takes around 230MB for me.
Miniflux (which I might write an article for in the future) takes 35MB, its postgres server 80MB.

To easily see ram usage per user (assuming you run services under separate users), you can use smem -uk, using PSS would be most fitting I suppose. Measuring RAM consumption is not as easy as one might think on Linux because of shared libraries (https://stackoverflow.com/questions/22372960/is-this-explanation-about-vss-rss-pss-uss-accurate).

@termermc
Copy link
Contributor

termermc commented Jul 2, 2021 via email

@wdunkelheit
Copy link

Pleroma can vary in memory usage based on how busy the instance is. But IIRC from playing with it in the past it never exceeded 300MB for a bare instance.

@uranderu
Copy link
Contributor

uranderu commented Jul 7, 2021

I like the idea a lot. But sometimes it is a tough one because you are dealing with a lot of variable here :P ie Distro, Virtualization (Yes/no? Containers or fully-fledged VM's?), etc.

@termermc
Copy link
Contributor

termermc commented Jul 7, 2021 via email

@ghost
Copy link

ghost commented Jul 15, 2021

If you are running a server and 5-10 people use it, most likely the RAM usage in such a use-case would be representative of what most people following the tutorial will be experiencing.

Well that's pretty much exactly my case. Here's what I got:

  • Synapse: 200-400 MB while idle
  • Invidious: ~300 MB (Seems to be tarding atm, usually only around 200MB)
  • Libr*ddit: 180 MB
  • Gitea: 100-150 MB; can destroy CPU when lots of traffic, make sure to install fail2ban
  • Peertube: 130 MB, sometimes goes up during traffic
  • Uwsgi (SearX): 100 MB
  • Prosody: 10-20 MB
  • Nginx: 20-30 MB
  • Agate (Gemini), Mail server (Postfix, OpenDKIM, Spamassassin, Dovecot), Filtron (bot filter for searx): Literally nothing

These all use up very little CPU most of the time except Synapse because it's soyware

NOTE: This is all on an Arch server with a pretty heavy amount of traffic (tards shill my stuff on le 4chinz), and quite a few users on my Matrix server. Will likely vary a bit for Debian servers but this is a general good guideline i guess

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants