Reducing hosting footprint

florence-social / mastodon-fork

Florence's fork of Mastodon

GNU Affero General Public License v3.0

138 stars 15 forks source link

Reducing hosting footprint #29

Open clarfonthey opened 5 years ago

clarfonthey commented 5 years ago

Right now, Mastodon takes a lot of resources to host, and there are probably a bunch of low-hanging fruit we can work on.

ghost commented 5 years ago

This is a big issue but a small change you can make towards this goal is maybe taking sir goops docker file which produces a smaller docker image that has jemalloc baked in (which uses less ram) https://git.sergal.org/Sir-Boops/docker-mastodon

ariasuni commented 5 years ago

Suggestions:

Rewrite streaming API in another language (maybe already in progress)
Use something else than ElasticSearch (maybe see how Plume do it)
Use something else than Puma (see https://github.com/tootsuite/mastodon/pull/8734 for example)
Find critical parts of the code that can be rewritten in a more efficient language

Also I heard Switter made changes to accommodate their very rapid growth at the beginning, so they may want to work with us and upstream some of their changes.

igalic commented 5 years ago

I don't know if it's currently sensibly possible, but perhaps being able to split out backend and frontend may help with this, a i'm sure they have very different needs. Glitch-soc has an issue here: https://github.com/glitch-soc/mastodon/issues/744

However, i'm not sure that'll necessarily help with making this any easier to install…

kaniini commented 5 years ago

regarding ES: There is already a patch for Mastodon which uses PostgreSQL in a similar way as Pleroma does to implement fulltext search. You can find out more by talking to gled@mastodon.host.