Elasticsearch vs. OpenSearch: Performance and resource utilization analysis | Elastic Blog
#performance
After months without working search, I deleted the elasticsearch 8 container and created a new one with elasticsearch 9. Currently hydrating it with tootctl search deploy. 12.721.688 documents, 2 hours left.
I hate self hosting. (Still thankful to everyone who makes it possible.)
Managing agentic memory with Elasticsearch - Elasticsearch Labs
https://www.elastic.co/search-labs/blog/agentic-memory-management-elasticsearch
test toot for elasticsearch
Today I spend a few hours fixing a server crash in my project with the most users. We moved the app to a new server yesterday. Today at lunch it crashed (right during Mittagsjournal..). The log was full of ElasticSearch errors complaining about 6278198379712 being bigger than maxint. Fair enough. After some digging I found searches requesting this hugh number as the page param. Which makes no sense, we don't have that much content. The quick fix was to limit page to 100. Then the proper …
⚡ Uses up to 30x less RAM and 15x less disk space than Elasticsearch and Grafana Loki. Capacity and performance scale linearly with available resources - runs smoothly on Raspberry Pi and on servers with hundreds of CPU cores and terabytes of RAM. Scales horizontally to hundreds of nodes in cluster mode.
🔧 Zero-config single executable setup - no tuning required for VictoriaLogs or the operating system. Reasonable defaults automatically adjust for available CPU and RAM resources. Much easier to set up and operate compared to Elasticsearch and Grafana Loki.
🔌 Accepts logs from popular collectors including Fluentbit, Fluentd, Logstash, Vector, Promtail, #OpenTelemetry, DataDog Agent…