Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ot
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
61.
▲
by
ot
1y ago
> Either the threads all do their separate “actually log” But why? Often the purpose is just to log a "been here" signal with some additional details for diagnostics. You don't need to include an accumulation of everything
62.
▲
by
ot
1y ago
No, the timer is still global (that's why you need the compare-and-swap). But the threads only need to do reads most of the time, and reads do not cause contention. Writes do. It looks something like this (pseudocode): static std
63.
▲
by
ot
1y ago
There is an additional benefit to throttling by time, it is a lot easier to do it efficiently in multithreaded environments. If you log by count, you need a global counter for that event (you could do thread-local, but then your logging vol
64.
▲
by
ot
1y ago
`NoDestructor` just ensures that the destructor is not called on the wrapped object, but you still need to manage the lifetime. If you look at the example, its recommended usage is with a function static. In other words, it's a utility
65.
▲
by
ot
1y ago
Yes, thanks for the clarification, what I probably should have said is that the trick is basically syntactic sugar to declare a scoped global static variable, and as such it inherits all the problems of global static variables.
66.
▲
by
ot
1y ago
Not with any of the Clang versions I tried, but last time I checked it was a couple of years ago.
67.
▲
by
ot
1y ago
That's a nice trick, but contrary to function statics, it is susceptible to SIOF. This kind of optimization is useful only on extraordinarily hot paths, so I wouldn't generally recommend it. > On ARM, such atomic load incurs a
68.
▲
Meta Superintelligence – Leadership Compute, Talent, and Data
(semianalysis.com)
11 points
by
ot
1y ago
|
1 comments
69.
▲
by
ot
1y ago
I would guess to develop and test software that will ultimately run on a system with 64k page size.
70.
▲
Formalizing a proof in Lean using Github copilot and canonical [video]
(youtube.com)
2 points
by
ot
1y ago
|
0 comments
71.
▲
Qwen3 Embedding: Advancing Text Embedding and Reranking with Foundation Models
(arxiv.org)
1 points
by
ot
1y ago
|
0 comments
72.
▲
Sushi Roll: A CPU research kernel for micro-architectural introspection (2019)
(gamozolabs.github.io)
3 points
by
ot
1y ago
|
0 comments
73.
▲
by
ot
1y ago
> While the company insists that “nothing is shared unless you choose to post it,” the app nonetheless nudges people to share—and overshare—whether they fully realize it or not.
74.
▲
Formal Modeling and Analysis of Distributed (Event-Driven) Systems
(github.com)
2 points
by
ot
1y ago
|
1 comments
75.
▲
Linear scalable read-write lock
(uvdn7.github.io)
3 points
by
ot
1y ago
|
0 comments
76.
▲
by
ot
1y ago
On Linux you'd do this by sending a signal to the thread you want to analyze, and then the signal handler would take the stack trace and send it back to the watchdog. The tricky part is ensuring that the signal handler code is async-si
77.
▲
Apple airlifts 600 tons of iPhones from India 'to beat' Trump tariffs
(reuters.com)
10 points
by
ot
1y ago
|
0 comments
78.
▲
by
ot
2y ago
Karma is stored in a 16 bit integer. It overflowed.
79.
▲
by
ot
2y ago
Being more robust to fragile compiler optimizations is also a nontrivial benefit. An interpreter loop is an extremely specialized piece of code whose control flow is too important to be left to compiler heuristics. If the desired call struc
80.
▲
by
ot
2y ago
The fact that they categorize FNV-1a as "Good all-rounder, decent speed and collision resistance" was an immediate red flag for me. It does look like an article written more than 10 years ago.
81.
▲
Trump signs order to establish a sovereign wealth fund that could buy TikTok
(cnbc.com)
10 points
by
ot
2y ago
|
1 comments
82.
▲
Strobelight: A profiling service built on open source technology
(engineering.fb.com)
2 points
by
ot
2y ago
|
0 comments
83.
▲
by
ot
2y ago
That is a ridiculously well made video, thanks for sharing!
84.
▲
by
ot
2y ago
Nothing wrong with reposts, it's just useful to link to previous discussions for context :)
85.
▲
by
ot
2y ago
Previous discussion (Jun 2024): https://news.ycombinator.com/item?id=40753989
86.
▲
AWS re:Invent 2024 – Dive deep on Amazon S3 [video]
(youtube.com)
2 points
by
ot
2y ago
|
0 comments
87.
▲
by
ot
2y ago
Arrogance being one of the main criticisms in the article is a little ironic, coming from bcantrill.
88.
▲
by
ot
2y ago
What that code does is a per-byte-pair popcount, which is not what the POPCNT instruction does (it computes the popcount for the whole word). On processors with BMI2 the whole algorithm reduces to a PDEP as mentioned in another comment, but
89.
▲
by
ot
2y ago
I broadly agree with the thesis of the post, which if I understand correctly is that frame pointers are a temporary compromise until the whole ecosystem gets its act together and manages to agree on some form of out-of-band tracking of fram
90.
▲
Stack-based graph traversal ≠ depth first search
(11011110.github.io)
3 points
by
ot
2y ago
|
0 comments
More ›