3 ms·
Since you're here, I would really enjoy reading about the operational concerns about running V.L. for real (and my apologies for not digging into the repo for "
by mdaniel 3y ago
Since you're here, I would really enjoy reading about the operational concerns about running V.L. for real (and my apologies for not digging into the repo for "code is the truth" type docs):
- Does it use its own flatfile system, or some novel storage mechanism?
- Any plans on offering "S3-ish" store for practically unlimited storage (at, of course, the risk of latency for fetches)?
- Does it tolerate running on NFS?
- valyala 3y ago- VictoriaLogs uses its own storage format, which is inspired by ClickHouse storage format [1]. This is basically a column storage format optimized for structured logs with arbitrary number of fields. - Yes, VictoriaLogs is going to support object storage. See our roadmap [2] - VictoriaLogs should work good on NFS. It writes data to disk in big sequential chunks, which should work optimally on NFS. It reads data in parallel from multiple threads during queries. This should help increasing query performance on high-latency storage such as NFS. [1] https://clickhouse.com/docs/en/development/architecture https://clickhouse.com/docs/en/development/architecture [2] https://docs.victoriametrics.com/VictoriaLogs/Roadmap.html https://docs.victoriametrics.com/VictoriaLogs/Roadmap.html