broken_broken_

6 ms·

1.
Optimization tales with CockroachDB: the slow logout(gaultier.github.io)
1 points by broken_broken_ 3mo ago|0 comments
2.
Optimization tales with CockroachDB: the slow password reset flow(gaultier.github.io)
2 points by broken_broken_ 3mo ago|0 comments
3.
I sped up the test suite by 2x with one simple change(gaultier.github.io)
2 points by broken_broken_ 3mo ago|0 comments
4.
by broken_broken_ 5mo ago
It depends how much the code uses manually spawned goroutines, and how complex the lifecycle of these goroutines is… in big codebases such as kubernetes, docker, etc, it has been a problem. There have been research papers and blogs about t
5.
by broken_broken_ 6mo ago
Interesting to see an ebpf approach to this idea, some time ago I did the same with Dtrace: https://gaultier.github.io/blog/detecting_goroutine_leaks_wi... However I did not think of observing the ‘castgstatus’ runtime
6.
by broken_broken_ 6mo ago
The name clashes with a similar project that has existed for decades: https://zeroc.com/ice
7.
The production bug that made me care about undefined behavior(gaultier.github.io)
1 points by broken_broken_ 9mo ago|0 comments
8.
Detecting Goroutine Leaks with DTrace(gaultier.github.io)
2 points by broken_broken_ 9mo ago|0 comments
9.
by broken_broken_ 9mo ago
I am not an expert in incident reaction, but I thought the safe way was to image the affected machine, turn it off, take a clean machine, boot a clean OS image with the affected image mounted read only in a VM, and do the investigation like
10.
by broken_broken_ 9mo ago
Nice article, thank you. Did you also consider using bpftrace while debugging? I do not have much experience with it, but I think you can see the kernel call stack with it and I know you can also see the return value (in eax). That would b
11.
by broken_broken_ 10mo ago
Author here, thanks for the feedback on legibility, I have now just learned about the CSS `tab-size` property to control how much space tabs get rendered with. I have reduced it, should be better now.
12.
A million ways to die from a data race in Go(gaultier.github.io)
4 points by broken_broken_ 10mo ago|0 comments
13.
How to reproduce and fix an I/O data race with Go and DTrace(gaultier.github.io)
1 points by broken_broken_ 1y ago|0 comments
14.
Observe live SQL queries in Go with DTrace(gaultier.github.io)
3 points by broken_broken_ 1y ago|0 comments
15.
by broken_broken_ 1y ago
I love a good SIMD article! Just one point about testable assembly: I like the Golang guidelines which require to write a Go version before implementing the same in assembly. That way there is a baseline to compare with in terms of correctn
16.
by broken_broken_ 1y ago
Your are right about shadowing: I just checked and the go specification calls it “redeclaration” and it works as you described: > Redeclaration does not introduce a new variable; it just assigns a new value to the original I added a ment
17.
A subtle bug with Go's errgroup(gaultier.github.io)
27 points by broken_broken_ 1y ago|19 comments
18.
by broken_broken_ 1y ago
I agree with the premise, just use a specific version of your dependencies, that’s generally fine. However: You absolutely do need a lock file to store a cryptographic hash of each dependency to ensure that what is fetched has not been tamp
19.
by broken_broken_ 1y ago
I wrote a toy Kotlin compiler, for fun. Then one day a Jetbrains employee opens an issue which only says: “Why? Just why?”. Maybe it’s the language barrier… but I did not find that particularly polite. On the other hand I open sourced my b
20.
by broken_broken_ 1y ago
Miri and Valgrind will usually catch this kind of issue. I did lots of work mixing C and Rust and that tripped me as well at the beginning. I wrote about it if someone is interested: https://gaultier.github.io/blog/perh
21.
by broken_broken_ 1y ago
I wrote a blog article about exactly this, using a C++ class from C++, C and Rust: https://gaultier.github.io/blog/rust_c++_interop_trick.html
22.
by broken_broken_ 1y ago
I have implemented polling against a cluster of mixed mariadb/mysql databases which do not offer listen/notify. It was a pain in the neck to get right. - The batch size needs to be adaptative for performance, latency, and recoveri
23.
An optimization and debugging story with Go and DTrace(gaultier.github.io)
2 points by broken_broken_ 1y ago|0 comments
24.
by broken_broken_ 1y ago
The x64 assembly would probably work natively on the Mac, no need for docker, provided the 2 syscall numbers (write and exit) are adjusted. Which llms can likely do. If it’s an ARM Mac, under Rosetta. Otherwise directly.
25.
by broken_broken_ 1y ago
I low key want to buy t-shirts of these now.
26.
by broken_broken_ 1y ago
About not having perf on macOS: you can get quite far with dtrace for profiling. That’s what the original flame graph script in Perl mentions using and what the flame graph Rust reimplementation also uses. It does not have some metrics like
27.
A subtle data race in Go(gaultier.github.io)
1 points by broken_broken_ 1y ago|0 comments
28.
What should your mutexes be named?(gaultier.github.io)
6 points by broken_broken_ 1y ago|0 comments
29.
by broken_broken_ 1y ago
Reading the article I thought exactly the same! I‘d be curious to know how much time the same would take with zfs.
30.
by broken_broken_ 1y ago
I have worked for financial services companies that used FreeBSD both in EC2 and on the metal in data centers (self managed). The two features we used all the time were zfs and jails. Each service ran in its own jail for isolation. One (no

More ›