Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
valyala
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
31.
▲
VictoriaTraces: Tracing, Observability, and OpenTelemetry0
(rtfm.co.ua)
2 points
by
valyala
5mo ago
|
0 comments
32.
▲
Understanding the Go runtime: the "select" statement
(internals-for-interns.com)
4 points
by
valyala
5mo ago
|
0 comments
33.
▲
by
valyala
5mo ago
https://lwn.net is a goldmine of great contents about Linux kernel. Let me explain why I post links to posts from https://internals-for-interns.com . I hate AI slop. The author of these posts uses AI for generating t
34.
▲
by
valyala
5mo ago
> This AI slop, on which I was able to quickly find four mistakes Could you provide more details about these mistakes?
35.
▲
Understanding the Linux Kernel: The Linux Kernel Startup
(internals-for-interns.com)
80 points
by
valyala
5mo ago
|
21 comments
36.
▲
by
valyala
5mo ago
VictoriaMetrics CTO here. We at VictoriaMetrics took another approach. We tried using ClickHouse as a database for metrics in 2017, but then decided implementing a specialized database for metrics. This database uses ClickHouse architecture
37.
▲
Lies, damned lies, and Elastic's benchmarks
(gouthamve.dev)
2 points
by
valyala
5mo ago
|
0 comments
38.
▲
Understanding the Go Runtime: Slices, Maps, and Channels
(internals-for-interns.com)
3 points
by
valyala
5mo ago
|
0 comments
39.
▲
Claude Code: Creating Kubernetes Debugging AI Agent for VictoriaMetrics
(rtfm.co.ua)
1 points
by
valyala
5mo ago
|
0 comments
40.
▲
Zero-config Go heap profiling
(coroot.com)
2 points
by
valyala
6mo ago
|
0 comments
41.
▲
Understanding the Go Runtime: The Network Poller
(internals-for-interns.com)
5 points
by
valyala
6mo ago
|
0 comments
42.
▲
Optimizing Tail Sampling in OpenTelemetry with Retroactive Sampling
(victoriametrics.com)
19 points
by
valyala
6mo ago
|
0 comments
43.
▲
by
valyala
6mo ago
I'm core developer at VictoriaMetrics. This information is one click away - just click my name here.
44.
▲
by
valyala
6mo ago
Yes, there is a solution for masking the read latency at object storage - to run many readers in parallel. I tweeted about it some time ago - https://x.com/valyala/status/1965093140525715714
45.
▲
by
valyala
6mo ago
Interesting solution! According to the provided numbers at "query latency" chapter, the query over cold data, which selects samples for 497 time series over 6 hours time range takes 15 seconds if the queried data isn't availa
46.
▲
by
valyala
6mo ago
There is another approach for solving this issue - to use increase_pure() function from MetricsQL - https://docs.victoriametrics.com/metricsql/#increase_pure . Of course, you need to switch to VictoriaMetrics, since Mi
47.
▲
by
valyala
6mo ago
It is interesting why Airbnb uses vmagent for streaming aggregation and didn't switch from Mimir to VictoriaMetrics. This could save them a lot of costs on infrastructure and operations, like in cases of Roblox, Spotify, Grammarly and
48.
▲
Filesystems: Btrfs
(internals-for-interns.com)
2 points
by
valyala
6mo ago
|
0 comments
49.
▲
Agentic Coding at ClickHouse
(clickhouse.com)
1 points
by
valyala
6mo ago
|
0 comments
50.
▲
by
valyala
6mo ago
This is a good alternative for those who wants storing petabytes of historical logs, metrics or traces in VictoriaLogs, VictoriaMetrics and VictoriaTraces, and wants saving 2x-4x on the persistent storage pricing (compare EBS pricing to S3
51.
▲
Understanding the Go Runtime: The System Monitor
(internals-for-interns.com)
2 points
by
valyala
6mo ago
|
0 comments
52.
▲
Porting Go's strings package to C
(antonz.org)
5 points
by
valyala
6mo ago
|
0 comments
53.
▲
Top Things Not to Do at KubeCon
(medium.com)
2 points
by
valyala
7mo ago
|
0 comments
54.
▲
Understanding the Go Runtime: The Garbage Collector
(internals-for-interns.com)
2 points
by
valyala
7mo ago
|
0 comments
55.
▲
Porting Go's io package to C
(antonz.org)
1 points
by
valyala
7mo ago
|
0 comments
56.
▲
Benchmarking Kubernetes Log Collectors: Vector, Fluent Bit, OTEL Collector, etc.
(victoriametrics.com)
2 points
by
valyala
7mo ago
|
0 comments
57.
▲
by
valyala
7mo ago
If the server cannot keep up with the given workload because of some bottleneck (CPU, network, disk IO), then it cannot guarantee any response times - incoming queries will be either rejected or queued in a long wait queue, which will lead
58.
▲
Having fun with the Go source code
(jespino.github.io)
3 points
by
valyala
7mo ago
|
0 comments
59.
▲
Understanding the Go Runtime: The Scheduler
(internals-for-interns.com)
158 points
by
valyala
7mo ago
|
48 comments
60.
▲
Last Year in Container Security
(nanovms.com)
3 points
by
valyala
7mo ago
|
0 comments
More ›