As a single user instance #mastoadmin, seeing the insane influx in resource usage just by enabling #elasticsearch makes me somehow think this isn't the solution people are hoping for in terms of searchability...how do servers like mastodon.social handle it? AFAIK, It uses HALF of your systems ram by default...if #mastodon is using the other half...the servers gonna grind to a halt. Just sayin. 🤷🏻♂️🤦🏻♂️from 40-50% without elasticsearch, straight to 80% with it, on a SINGLE USER instance. Yikes.
@BeAware Elasticsearch uses Java and Java is known to be a memory hog. I don't know they chose that language but they did.
Elasticsearch doesn't seem to be for single nodes (although, maybe it can work for that scenario). With it, you can have multiple shards which you can house in different servers in a cluster.
It also appears to use more resources when it's setup to index content in "real-time" (one second) than if you have a larger interval (although, there is the trade-off that it might take time for something to become searchable).
I hope that helps.
