consuming logs

set up both Loki and VictoriaLogs, will wait for a day and see how it performs after consuming many kiloliters of logs

I suspect that memory usage might go quite a bit up, surprisingly enough it consumes less memory and CPU than Loki at the moment

didn't notice this initially, but it also has a "beta query builder"

200k logs/second ftw

comment maxxing on pull requests

16 million logs later, the results are insane

VictoriaLogs still consumes less resources than Loki, runs queries 100x faster and yet supports high-cardinality indexes with full-text search

same query over 16M of logs on both Loki and VL:

Grafana Loki: 10-11s
VictoriaLogs: 250ms

official Jaeger integration just got approved today too

we've never been so early

https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8988

dear god…

7 seconds away

7 seconds away...

vibecoding in it's purest form

I'm done, anysphere

I use neovim, btw

https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8988

victoriatraces
victoriatraces

I've collected roughly 100M logs over the last few days in both Loki and VictoriaLogs

VictoriaLogs finally started to utilize a little more memory than Loki

Query time amazingly is still ~250ms for full-text search (not labels)

I don't even want to try running same query with Loki, it will just explode...

(it did explode)