Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
brancz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
brancz
3y ago
Oh we’ll make this more clear, actually only Linux 5.4 is required, Kubernetes is only to add more metadata. It still works just fine and we have customers running it outside of Kubernetes provisioned by ansible.
62.
▲
by
brancz
3y ago
Great question! That’s correct, for the moment we’re focusing on everything that happens in the backend. That said, the system will accept anything in the pprof format so I’d love to see something like “1% of users get profiled and data sen
63.
▲
by
brancz
3y ago
Haskell support should land sooner rather than later actually! We are very very close it’s just that the Haskell compiler unfortunately creates binaries that don’t comply to the x86 ABI. It’s not too dramatic though, it just shuffles around
64.
▲
by
brancz
3y ago
Great question! The big one that existing columnar databases can’t do (or not well), is the ability to search and aggregate on user defined dimensions (think prometheus-style labels). Influx 3.0 is the only other columnar database that is (
65.
▲
by
brancz
3y ago
Pricing is never final, so that feedback is valuable, thank you! If you want to schedule a chat I'd love to learn more about your use case and happy to figure out what works for you! https://calendly.com/frederic-brancz
66.
▲
by
brancz
3y ago
Thank you for the kind words! Try the product and let us know what you think! :)
67.
▲
by
brancz
3y ago
Thank you! Agreed, it's a real super power! The first time we got differential flamegraphs working we were so mesmerised that we could finally see exactly what the difference between a low and a high point (like a CPU spike) was, that
68.
▲
by
brancz
3y ago
Thank you! We'll work on the messaging on the website!
69.
▲
by
brancz
3y ago
@Dang can we merge this with the other ongoing thread on this? ( https://news.ycombinator.com/item?id=37832216 )
70.
▲
by
brancz
3y ago
Thanks for posting! We'll be hanging out in the comments all day if you have any questions or feedback!
71.
▲
by
brancz
3y ago
Great question! At the moment it is 30 days. We've had a few requests to make that configurable, but the reality is that the most costly part is to lay it out in an optimized way in the first place which happens very early on in the in
72.
▲
by
brancz
3y ago
Hey HN! Myself and several members of the Polar Signals team have been long time Observability ecosystem maintainers of projects such as Prometheus, Thanos, Cortex, Kubernetes and many more. In 2018 we read the "Google-Wide Profiling&q
73.
▲
by
brancz
3y ago
Love lensm! I've used it on several occasions to teach people about inlining, bounds check removals, and other performance related topics that are best highlighted by actually seeing differences in assembly. I find it's easier for
74.
▲
Profiling Python and Ruby Using eBPF
(polarsignals.com)
38 points
by
brancz
3y ago
|
2 comments
75.
▲
by
brancz
3y ago
Thanks for mentioning that! We'll do that. To clarify the current state: dotnet and jvm require enabling flags, python fully works without any changes (as of 2 weeks ago blog post on how we made this possible is about to be released).
76.
▲
by
brancz
3y ago
Since pprof is supported you could use parca-agent [1], an eBPF-based profiler that I happen to work on, as when you browse the debug UI on port 7071 you can download a pprof formatted profile for any process running on the machine. Support
77.
▲
by
brancz
3y ago
Pretty neat! Tried profiling it since it aims for high performance use cases. Love how far we can get with standards in software engineering that we can just take this new language/runtime and just profile it! Wrote a quick blog post o
78.
▲
by
brancz
3y ago
Is there any indication that it’s possible to build subatomic size transistors? Last I checked the data, transistors are already only a few atoms in size (silicon and carbon atoms are somewhere in the 0.3nm range), and it was a widely held
79.
▲
Correctly Profiling Node.js with Zero-Instrumentation
(polarsignals.com)
6 points
by
brancz
3y ago
|
0 comments
80.
▲
by
brancz
3y ago
In its original form as in "transistors double every two years" it certainly already seems over. Apple silicon is at 5mn today, and Intel claims they'll conquer 3mn by 2030, so even these facts and theoretical statements alre
81.
▲
by
brancz
3y ago
Interesting! Might give this a try some time. I occasionally find myself needing a Linux environment, and my primary device is an arm64 mac, I think it could be useful for that. More generally what do you see being the prime use cases?
82.
▲
by
brancz
3y ago
Neat! I enjoyed using gitpod a few times, this seems similar. How do they compare?
83.
▲
by
brancz
3y ago
In a world of shared GPUs, what tools do people use to profile their GPU workloads. Are there code level profilers like for CPUs? I typically hear that people don’t often have issues with the code running on the GPU itself but rather ensuri
84.
▲
by
brancz
3y ago
My favorite change (even though it's not listed in the changelog), is that just-in-time compiled code now has frame pointers[1], making Julia code much more debuggable. Profilers, debuggers, etc. all can now work out of the box. Extra
85.
▲
by
brancz
3y ago
For the always-on open-source profiler we happen to work on at work we had to do similar things and it was even more involved since we base the whole thing on eBPF to lower the overhead and therefore needed to get the verifier to accept it.
86.
▲
by
brancz
4y ago
It’s the same in spirit, but I just find the A/B partitions easier to reason about. To me it’s about minimizing factors.
87.
▲
by
brancz
4y ago
A couple of small things, but primarily I don’t think it actually embraced immutability in the same way. CoreOS container Linux used A/B partitions for updating truly immutably. Partition B didn’t boot? Just boot A again. Fedora CoreOS
88.
▲
by
brancz
4y ago
Yes this is a direct fork. I happened to have been a CoreOS Berlin employee and know the kinfolk folks (now acquired by Microsoft) that did this fork after the Red Hat acquisition very well. I’m very glad they did, a lot of things I liked a
89.
▲
by
brancz
4y ago
Original creator of both of those here. I recommend just generating things out straight with the `jsonnet -m` command, and then doing `kubectl diff` on a PR and apply on merge. Scaled huge amount of infra this way and it’s easily understand
90.
▲
Exploring Go's Profile-Guided Optimizations
(polarsignals.com)
9 points
by
brancz
4y ago
|
0 comments
More ›