Denis Onopko

1K posts

Denis Onopko banner
Denis Onopko

Denis Onopko

@candyboobers

Logging must be cheap, build new generation observability database https://t.co/X5Q2bC26F6

Berlin, Germany Katılım Ekim 2017
81 Takip Edilen63 Takipçiler
Denis Onopko
Denis Onopko@candyboobers·
@glcst and it makes the language debates pointless! we all meet in lldb anyway
English
0
0
2
310
Glauber Costa
Glauber Costa@glcst·
LLVM is such a cool technology. Easy to miss the point: By having an intermediate representation of your program, you can very easily add new frontends. It allows improvements in one ecosystem to make all others better, and it allows for amazing experimentation because you don't start from scratch. Amazing tech. I wish more people would draw lessons from it.
English
6
3
106
7.4K
Denis Onopko
Denis Onopko@candyboobers·
@glcst and yes, the nature of append only data makes it simple, but not easy. and in EU we have to think about removing designated pages due to GDPR
English
0
0
0
16
Denis Onopko
Denis Onopko@candyboobers·
@glcst lack of industrial wise knowledge. there is very few teams work on time aware LSM compaction. although for my storage I don't find it as the biggest problem, rather a resource management for dynamic nature of data blows me mind on an attempt to implement a buffer pool
English
1
0
0
21
Glauber Costa
Glauber Costa@glcst·
I want to talk to people who live a database-centric lifestyle.
English
21
1
87
7.9K
Denis Onopko
Denis Onopko@candyboobers·
@quolpr Writing to disk, ssd. Yes, it’s not fast, but it’s the beginning of the journey. Sprinters are not born, they get trained in years.
English
0
0
1
22
Sergey
Sergey@quolpr·
@candyboobers Is it ram reading? Disk reading? If disk, nvme or ssd? Even if disk, sounds still slow 🤔 But I think I miss a lot of context
English
1
0
0
35
Denis Onopko
Denis Onopko@candyboobers·
Throughput Ochi jumped from 300kb to 1.2mb per sec per CPU. First and the most reliable optimisation - do less. Less allocations, less compute. Removed a few intermediate states, moved a couple buffers to a stack. Writing a post with overview of the last optimisations.
English
1
0
2
89
Denis Onopko
Denis Onopko@candyboobers·
@justinmk it's decent, but the toolchain is weaker. they are not focused on cross compile, the graphic programmers care only about windows
English
0
0
5
949
justinmk
justinmk@justinmk·
rn Zig is looking like the HR side of my pinned tweet. totally unrelated, how's Odin's cross-compilation + C interop + build speed, these days?
English
9
1
75
10.6K
Denis Onopko
Denis Onopko@candyboobers·
No it’s not. Operational complexity and query API is not suitable for observability. We must deliver new engine.
Charity Majors@mipsytipsy

Go read this post from Mat Duggan right now -- "@ClickhouseDB is Winning the Observability Wars". Go! I'll wait. matduggan.com/clickhouse-is-… "Every other observability backend I've worked with mutates as it grows... ClickHouse at 10 TB a day looks like ClickHouse at 1 TB a day with more shards. That's it. That's the pitch. That's the whole reason I'm writing this." Duggan's piece is a riot from start to finish. He talks you through all the pain of scaling Elastic, LGTM, and Datadog, and shows why a little tiny bit of upfront effort buys you SO MUCH EASE down the road, as you scale indefinitely. Why am I boosting Clickhouse's reputation like this? Because it isn't just fucking Clickhouse, you guys. Duggan just discovered what it's like to use observability backed by a columnar storage engine. We've been writing about this since the Year of Our Lord 2016. We wrote about it in the first edition of "Observability Engineering". We called it "Observability 2.0" a couple years back. We invited Clickhouse to contribute a guest chapter to the second edition of "Observability Engineering." I was on a panel at their conference last month. THIS IS WHY. This is the same way Honeycomb is built. But if you want to run and scale your own, yeah, you should fucking use Clickhouse! I don't mean to be all "I told you so", but look! what a difference! this shit makes! it can even make a grizzled logs warrior like Mat fall in love. YES, IT IS DIFFERENT. YES, IT IS EXCITING. If you're stuck using a product that was designed twenty years ago, maybe you too should give @ClickHouseDB -- or @honeycombio -- a shot.

English
0
0
0
51
Denis Onopko
Denis Onopko@candyboobers·
There is no such thing as „easy readable code“. There is a pattern you got used to and don’t feel comfortable to learn new approach. We accumulate data instead of chunks processing because we got used to it. We learned a lot of bad memory management practices
English
1
0
2
180
Denis Onopko
Denis Onopko@candyboobers·
@chronark They can, but it will decline the price a lot. Retailers don’t have enough money to buy out, while smart money don’t come for it
English
0
0
2
2.2K
chronark
chronark@chronark·
can anyone ELI5 why it's all stock? since spacex is now publicly traded, can't they just sell the stock immediately?
SpaceX@SpaceX

SpaceX has exercised the option to acquire @cursor_ai in an all-stock transaction with the goal of building the world’s most useful AI models. For the past few months, SpaceXAI has been jointly training a model with Cursor, which will be released in Cursor and Grok Build soon. We look forward to working closely with the Cursor team to advance our frontier AI capabilities

English
30
3
188
65.3K
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
Good read, I think Dave and I would get along just great. I’m also firmly in the camp of AI is great and we should all be using it but we need better measured outcome-oriented analysis of it. curlewis.co.nz/posts/lines-of…
English
17
15
300
33.9K
Denis Onopko
Denis Onopko@candyboobers·
Learning more from CMU and Andy Pavlo (big guy) found static allocations are regular thing for databases, while tigerbeetle did it open to the rest of the world. there some diverges, Postgres can crash a query because of whatever, but not OOM
English
0
0
0
32