3 ms·
I've been benching it in production. On a 1core 2gb vps it can do around 1200 logs/sec. Compared to ELK, we're saving several hundred $ per month.
by tmikaeld 7y ago
I've been benching it in production.
On a 1core 2gb vps it can do around 1200 logs/sec.
Compared to ELK, we're saving several hundred $ per month.
- chucky_z 7y agoIf you can't do 1200 logs/sec with that hardware + elasticsearch, you've done something horrendously wrong. You can do 1200 logs/sec with a container limited to 1 core and 256mb of memory running elasticsearch.
- Xorlev 7y agoReally depends on the size of each log and the complexity of the tokenizers. With 1 core you have time budget of less than a millisecond per log statement for processing and that doesn't include the relevant ES/Lucene operational overheads. This is extremely doable for some workloads, but not others. Really depends on what you're stuffing in.
- tmikaeld 7y agoThe savings are in RAM costs due to ELK stack basically not running under 4GB. And larger logs with stack trace are much slower compared to Loki. There's a reason there is no cheap ELK services.