Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
valyala
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
40 ms
·
481.
▲
by
valyala
7y ago
While there are many similar clustered open source TSDB solutions on the market - Thanos, Cortex, M3DB - VictoriaMetrics cluster provides the following benefits comparing to these solutions: - It is optimized for ease of use. - It is self-c
482.
▲
Cluster version of VictoriaMetrics – horizontally scalable time series database
(github.com)
7 points
by
valyala
7y ago
|
2 comments
483.
▲
by
valyala
7y ago
TimescaleDB could fit your workload if PostgreSQL fits you. The main issue with PostgreSQL and TimescaleDB is big amounts of storage space required for huge time series data volumes. There are reports that storing data on ZSF can reduce the
484.
▲
Twitter engineering blog: Democratizing data analysis with Google BigQuery
(blog.twitter.com)
2 points
by
valyala
7y ago
|
0 comments
485.
▲
by
valyala
7y ago
> Now you're screwed for some time until other people pick it back up depending on demand While the situation isn't good, it is still better than the situation when closed-source project is abandoned (for instance, old Windows
486.
▲
by
valyala
7y ago
Does this mean that small teams usually produce better code than bigger teams?
487.
▲
by
valyala
7y ago
It is interesting to look at known examples of open source projects suffered from bus factor. Open source projects allow fixing the bug on your own. Then the bugfix may be pushed to the original project. Popular abandoned projects may be fo
488.
▲
Ask HN: Why are successful open source projects usually developed by small teams
29 points
by
valyala
7y ago
|
13 comments
489.
▲
New encodings to improve ClickHouse efficiency
(altinity.com)
2 points
by
valyala
7y ago
|
0 comments
490.
▲
by
valyala
7y ago
While logs and metrics have common parts, they are quite different beasts. It is quite expensive producing and storing logs for frequently changing metrics such as requests rate or response latency on highly loaded system with millions of r
491.
▲
by
valyala
7y ago
I'd recommend taking a look at ClickHouse for storing and analyzing billions of ad-tech raw events in real time. There is no need in grouping them beforehand, since ClickHouse is able to scan billions of rows per second per server. See
492.
▲
by
valyala
7y ago
Prometheus metrics exposition format supports user-defined timestamps [1]. There is an alternative time series database - VictoriaMetrics - which supports data ingestion in Influx line protocol, while providing Prometheus querying API with
493.
▲
Comparing Thanos to VictoriaMetrics Cluster
(medium.com)
2 points
by
valyala
7y ago
|
0 comments
494.
▲
by
valyala
7y ago
Go is awesome programming language, since it is simple, readable and provides good tooling - code verification (vet), code formatting, testing, benchmarking, tracing, race detector, profiling - out of the box. Go encourages writing simple s
495.
▲
by
valyala
7y ago
Where to store time series data for further analysis? It is possible to use Prometheus for this - see https://medium.com/@valyala/analyzing-prometheus-data-with-e...
496.
▲
Lickhouse-local: The power of ClickHouse SQL in a single command
(altinity.com)
2 points
by
valyala
7y ago
|
0 comments
497.
▲
GitHub – fast zstd compressor in pure Go
(github.com)
4 points
by
valyala
7y ago
|
0 comments
498.
▲
GitHub – VictoriaMetrics: fast time series database compatible with Prometheus
(github.com)
3 points
by
valyala
7y ago
|
0 comments
499.
▲
by
valyala
7y ago
People don't care who owns Go. They just write awesome software in Go such as Docker, Kubernetes, Prometheus, Grafana and VictoriaMetrics [1]. Go authors created simple, clear and productive programming language. Community-driven desig
500.
▲
by
valyala
7y ago
There are two versions of VictoriaMetrics: single-node and cluster. Both versions are easier to configure and operate comparing to Thanos, Uber M3 and Cortex. Single-node version is the easiest from operations point of view - just run a sin
501.
▲
VictoriaMetrics: Achieving better compression than Gorilla for time series data
(medium.com)
1 points
by
valyala
7y ago
|
0 comments
502.
▲
ClickHouse as a Replacement for Elk, BigQuery and TimescaleDB
(pixeljets.com)
2 points
by
valyala
7y ago
|
0 comments
503.
▲
by
valyala
7y ago
Our customers successfully use VictoriaMetrics [1] in production as a long-term remote storage for big amounts of time series data from Prometheus. We are going to open source VictoriaMetrics soon. [1] https://github.com/Vic
504.
▲
by
valyala
7y ago
There is a chproxy [1] - a proxy that is able to balance inserts and selects across ClickHouse nodes / replicas. Then client applications shouldn't know anything about ClickHouse cluster topology - they just talk to chproxy. [1]
505.
▲
by
valyala
7y ago
Clickhouse cluster can run without Zookeeper and without replication. Data durability may be provided by using durable storage such as Google Compute Engine disks [1]. Data ingestion process may be accelerated without resorting to Kafka - j
506.
▲
by
valyala
7y ago
We prefer Google Cloud durable persistent storage. It may be started from a few GBs and then resized online up to 64TB per instance. This allows saving money by resizing disks only when needed. Such disks cost $40/TB/month. See h
507.
▲
by
valyala
7y ago
I'd recommend giving a try to VictoriaMetrics. It requires less hardware resources - RAM, CPU, disk - comparing to InfluxDB [1] and it supports PromQL - much nicer query language for typical time series queries comparing to InfluxQL or
508.
▲
by
valyala
7y ago
Consider moving to time series database with PromQL support. It is much easier to write typical queries over time series data in PromQL than in SQL or Flux. See https://medium.com/@valyala/promql-tutorial-for-beginners-
509.
▲
Measuring vertical scalability for time series databases in Google Cloud
(medium.com)
2 points
by
valyala
8y ago
|
0 comments
510.
▲
Lightweight alternative to github.com/prometheus/client_Golang/prometheus
(github.com)
3 points
by
valyala
8y ago
|
0 comments
More ›