thewisenerd

8 ms·

61.
by thewisenerd 1y ago
> Plan your release announcement during development this little section gives me so much... dread. on one hand, you have to be able to sell what you do; and on the other hand, if you cannot really quantify reasonable improvement to end u
62.
by thewisenerd 1y ago
theory: the amount of crap is increasing. the number of fucks given are decreasing.
63.
by thewisenerd 1y ago
indeed! most image processing golang services suggest/use jemalloc the top 3 from https://github.com/topics/resize-images (as of 2025-06-13) imaginary: https://github.com/h2non/imaginary/
64.
by thewisenerd 1y ago
for this particular deployment; we're only using the blob storage on azure. the deployments are on an on-prem kubernetes cluster with replicas=1 and strategy: recreate. throughput: not very heavy tbf.. one webhook request every 10-ish
65.
by thewisenerd 1y ago
> few nuggets scattered on the internet regarding how Stripe does things (ex. #1, #2, #3) and in general the conclusion is that they have a very demanding but very advanced engineering culture #3 is "What I Miss About Working at Str
66.
by thewisenerd 1y ago
ben, thanks for litestream! we're using it on production for a write-heavy interal use-case (~12GB compressed) for more than a year now; and it's costing us a couple hundred pennies per month (azure). excited to try the new change
67.
by thewisenerd 1y ago
https://archive.is/2xEGK
68.
by thewisenerd 1y ago
deleting data, has a cost. deleting data early after moving it to cold storage, has additional costs.
69.
by thewisenerd 1y ago
> having a decent way to get metrics from logs ad-hoc completely solves the metric cardinality explosion. last i checked, the span metrics connector[1] was supposed to "solve" this in otel; but i'm not particularly incline
70.
by thewisenerd 1y ago
> observing it will drastically impact the event this presumes 'metrics' are 'cheaper' than 'traces' / observability 2.0 from a setup standpoint; purely from an implementation perspective?
71.
by thewisenerd 2y ago
i mean.. from your blog post linked in the repo; this isn't eBPF based? https://clickhouse.com/blog/kubenetmon-open-sourced the data collection method says: "conntrack with nf_conntrack_acct"
72.
by thewisenerd 2y ago
so they didn't want to pay for AWS CloudWatch [1]; decided to roll their in-house network flow log collection; and had to re-implement attribution? i wonder how many hundreds of thousands of dollars network flow logs cost them; obvious
73.
The order of files in your ext4 filesystem does not matter(thewisenerd.com)
65 points by thewisenerd 2y ago|61 comments
74.
by thewisenerd 2y ago
good to know pub-sub shenanigans are ubiquitous lol here's my implementation from a while back with `setTimeout` like semantics; used it to avoid prop-drilling in an internal dashboard (sue me) https://gist.github.com/t
75.
by thewisenerd 2y ago
there's also similarly limits on width of elements, which I found out recently when trying to set a width to "45678910px" [1] [1] https://thewisenerd.com/works/45678910px.html
76.
by thewisenerd 2y ago
this builds upon PEP 723, which is "accepted", so it's likely here to stay. https://peps.python.org/pep-0723/ I've been very slowly migrating scripts to work with this, and `pipx run`. glad to know
77.
by thewisenerd 2y ago
as a former record holder (1m18s, 2015) it's been fascinating to see this number go down over the years
78.
by thewisenerd 2y ago
haha i added the following to my bashrc a few days ago for similar reasons; this forces me to be explicit about the cluster; now i mess up the wrong namespace instead :) if [[ -e "/opt/homebrew/bin/kubectl&quo
79.
by thewisenerd 2y ago
the "true spec is the data" is very powerful. for example, we translate our loosely OTEL-based telemetry into a format which was consumable by any otel collector. shim a few fields, et voila! can be read by Jaeger-UI. free trace t
80.
by thewisenerd 2y ago
yep; this is not built for mobile. you can check out a screenshot here: https://i.imgur.com/imMqde2.png
81.
Show HN: Visualizing Kubernetes Pods Distribution in Nodes(thewisenerd.com)
3 points by thewisenerd 2y ago|2 comments
82.
by thewisenerd 2y ago
this was a joke. referenced in the PR for this commit is tfa https://www.govtech.com/question-of-the-day/question-of-the-...
83.
by thewisenerd 2y ago
would like to know if someone's got a more objective approach; what we currently do is just a maxOf; take CostPerGB (memory) and CostPerCore (cpu); and costPerPod = max(pod.requests.cpu * CostPerCore, pod.requests.memory * CostPerGB) a
84.
by thewisenerd 2y ago
> not only was I no longer able to mint my own API tokens, the legitimate ones I’d initially generated still worked can someone explain what's meant by this? i presume the private key identified by the author still works, but will s
85.
Achieving 25% Compute Reduction with Time-Based Autoscaling(medium.com)
5 points by thewisenerd 2y ago|0 comments
86.
by thewisenerd 3y ago
discussed previously: https://lwn.net/Articles/962782/ https://news.ycombinator.com/item?id=39636915
87.
Kaslr offset exposure in Xen through world-readable /sys/kernel/notes(lore.kernel.org)
3 points by thewisenerd 3y ago|1 comments
88.
by thewisenerd 3y ago
https://web.archive.org/web/20240217123128/https://xeiaso.ne...
89.
by thewisenerd 3y ago
hug of death, archive link below: https://web.archive.org/web/20240217123128/https://xeiaso.ne...
90.
by thewisenerd 3y ago
`this` in javascript

More ›